Operation scheme creating method, operation scheme creating program and operation scheme creating device

Abstract

To automatically create an operation scheme.SOLUTION: A control device 1 that automatically executes an operation scheme creating process includes: an information managing unit that stores device standard information; an information receiving unit that receives an input of facility information including device information, connection information representing a connection relation between devices, and parent-child information representing a parent-child relation between the devices; a creation rule predicting unit that identifies, for each device, a first creation rule corresponding to each device by inputting information created by, for each device, utilizing any one of connection node information corresponding to the kind of each device, the device information on each device, the connection information on each device, and the parent-child information on each device to a learning model that has undergone a machine learning on teacher data including information created by utilizing any one of the connection node information corresponding to the kind of the device for learning, the device information on the device for learning, the connection information on the device for learning, and the parent-child information on the device for learning, and information representing a creation rule corresponding to the device for learning; and an operation scheme creating unit that creates a first operation scheme corresponding to the device based on the identified first creation rule.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present disclosure relates to a driving plan generating method, a driving plan generating program, and a driving plan generating device. [Background technology]

[0002] In design work for various plants (hereinafter also referred to as plant design work), for example, an operation plan designer interprets information obtained from the plant designer regarding the specifications of each piece of equipment that makes up the plant, information regarding the connection relationships of the plant flow, etc. (hereinafter also referred to as equipment information), as well as a draft operation plan, and designs an operation plan for the plant (hereinafter also referred to as operation plan design work).

[0003] The above-mentioned design work is made more efficient by using a design support system for each work, but there is no cooperation between multiple design support systems. Therefore, in the operation plan design work, for example, the operation plan designer may interpret information obtained from the plant designer and manually input it into the design support system (see Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2015-106317 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the above-mentioned operation plan design work, for example, depending on the scale of the plant, the number of diagrams on which the operation plan is described may become enormous. Therefore, in the operation plan design work, for example, it takes time to design the operation plan, and there is a possibility of human error such as failure to update due to design changes in the upstream process. Therefore, in the operation plan design work, for example, a method that enables automatic generation of the operation plan is desired. [Means for solving the problem]

[0006] The driving plan generating method of the present disclosure stores, in a storage unit, device standard information including a generating rule for a driving plan corresponding to each type and connection point information indicating attributes of connection points between the device corresponding to the type and other devices, accepts input of facility information including device information indicating one or more devices, connection information indicating a connection relationship between the one or more devices, and parent-child information indicating a parent-child relationship among the one or more devices, and generates a driving plan corresponding to at least one of the connection point information corresponding to a type of learning device, the device information corresponding to the learning device, the connection information corresponding to the learning device, and the parent-child information corresponding to the learning device. The computer executes a process of inputting, for each of the one or more devices, information generated using at least one of the connection point information corresponding to the type of each device, the device information corresponding to each device, the connection information corresponding to each device, and the parent-child information corresponding to each device into a learning model that has been subjected to machine learning of teacher data including information generated using any of the connection point information corresponding to the type of each device, the device information corresponding to each device, the connection information corresponding to each device, and the parent-child information corresponding to each device, to identify a first generation rule corresponding to each of the one or more devices, and generate a first operating plan corresponding to the one or more devices based on each of the identified first generation rules. Effect of the Invention

[0007] According to the driving plan generating method of the present disclosure, it is possible to automatically generate a driving plan. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating a configuration of an operation plan generating system 1000 according to the first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating a hardware configuration of the control device 1 in the first embodiment. [Diagram 3] FIG. 3 is a functional block diagram of the control device 1 in the first embodiment. [Figure 4]FIG. 4 is a block diagram of information stored in information storage area 130 in the first embodiment. [Diagram 5] FIG. 5 is a flowchart illustrating the information preparation process according to the first embodiment. [Figure 6] FIG. 6 is a flowchart illustrating the model generation process in the first embodiment. [Figure 7] FIG. 7 is a flowchart illustrating the facility information generation process according to the first embodiment. [Figure 8] FIG. 8 is a flowchart illustrating a main process for generating an operation plan in the first embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the device standard information 131. As shown in FIG. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the device standard information 131. As shown in FIG. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the device standard information 131. As shown in FIG. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the device standard information 131. As shown in FIG. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the device standard information 131. As shown in FIG. [Figure 14] FIG. 14 is a diagram for explaining a specific example of the operation plan rule information 132. As shown in FIG. [Figure 15] FIG. 15 is a diagram for explaining a specific example of the operation plan rule information 132. As shown in FIG. [Figure 16] FIG. 16 is a diagram for explaining details of the operation plan generation process in the first embodiment. [Figure 17] FIG. 17 is a diagram for explaining a specific example of the facility information 141. As shown in FIG. [Figure 18] FIG. 18 is a diagram for explaining a specific example of the facility information 141. As shown in FIG. [Figure 19] FIG. 19 is a diagram for explaining a specific example of the facility information 141. As shown in FIG. [Figure 20] FIG. 20 is a diagram illustrating a specific example of the device parent-child information 142. As shown in FIG. [Figure 21] FIG. 21 is a diagram for explaining details of the operation plan generation process in the first embodiment. [Figure 22] FIG. 22 is a diagram illustrating a specific example of step S24. [Figure 23] FIG. 23 is a diagram illustrating a specific example of step S24. [Figure 24] FIG. 24 is a diagram for explaining a specific example of the operation plan information 151. As shown in FIG. [Diagram 25] FIG. 25 is a diagram for explaining a specific example of the operation plan information 151. As shown in FIG. [Figure 26] FIG. 26 is a diagram for explaining a specific example of an output screen OP for the driving plan information 151 in the operation terminal 5. As shown in FIG. [Figure 27] FIG. 27 is a diagram illustrating a specific example of the teacher data DT. [Figure 28] FIG. 28 is a diagram illustrating a specific example of the teacher data DT. [Figure 29] FIG. 29 is a diagram illustrating a specific example of the teacher data DT. [Diagram 30] FIG. 30 is a functional block diagram of the control device 1 in the second embodiment. [Diagram 31] FIG. 31 is a block diagram of information stored in information storage area 130 in the second embodiment. [Diagram 32] FIG. 32 is a flowchart illustrating a main process of generating an operation plan in the second embodiment. [Diagram 33] FIG. 33 is a diagram illustrating a specific example of step S45. [Diagram 34] FIG. 34 is a diagram illustrating a specific example of step S45. [Diagram 35] FIG. 35 is a diagram illustrating a specific example of the input data DT0. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. However, such descriptions should not be interpreted in a limiting sense and do not limit the subject matter described in the claims. In addition, various changes, substitutions, and modifications can be made without departing from the spirit and scope of the present disclosure. In addition, different embodiments can be appropriately combined.

[0010] [Operation plan generation system 1000 according to the first embodiment] First, a description will be given of the configuration of a driving plan generating system 1000 in the first embodiment. Fig. 1 is a diagram for explaining the configuration of the driving plan generating system 1000 in the first embodiment.

[0011] The operation plan generating system 1000 is, for example, a system that automatically generates an operation plan for a plant. Specifically, the operation plan generating system 1000 has, for example, a control device 1 and an operation terminal 5 that can access each other via a network NW such as the Internet. Hereinafter, a case where an operation plan used in a water treatment plant including a sludge storage tank, a transfer pump, etc. is generated will be described, but the operation plan generating system 1000 may also generate an operation plan used in other plants such as a power plant or a chemical plant.

[0012] The operation terminal 5 is, for example, a PC (Personal Computer), and is a terminal through which an operator of the operation plan generating system 1000 (hereinafter, also simply referred to as an operator) inputs necessary information to the control device 1, and the like.

[0013] The control device 1 is, for example, a physical machine or a virtual machine, and is a device that performs a process of automatically generating a digitized driving plan (hereinafter, also referred to as a driving plan generation process).

[0014] Specifically, the control device 1 in this embodiment stores information (hereinafter also referred to as equipment standard information) in which a generation rule (hereinafter also referred to as generation rule) corresponding to each type of equipment corresponds to information (hereinafter also referred to as connection point information) indicating attributes of connection points between the equipment corresponding to each type and other equipment in a storage unit. Then, the control device 1 accepts input of facility information including, for example, information (hereinafter also referred to as equipment information or equipment list information) indicating one or more equipment (hereinafter also referred to as simply one or more equipment) for which an operation plan is to be generated, information indicating connection relationships between the one or more equipment (hereinafter also referred to as connection information or connection list information), and information indicating parent-child relationships among the one or more equipment (hereinafter also referred to as parent-child information or equipment parent-child information). Next, the control device 1, for example, refers to the equipment standard information stored in the storage unit, and specifies equipment standard information (hereinafter also referred to as first equipment standard information) corresponding to the type (hereinafter also referred to as first type) for each one or more equipment.

[0015] Thereafter, the control device 1 inputs, for each of one or more devices, information generated using at least one of the connection point information corresponding to the type of each device, the device list information corresponding to each device, the connection list information corresponding to each device, and the device parent-child information corresponding to each device, into the learning model that has been machine-learned with teacher data including, for example, connection point information corresponding to the type of device used in learning the learning model (hereinafter also simply referred to as learning device), device list information corresponding to the learning device, connection list information corresponding to the learning device, and device parent-child information corresponding to the learning device, and information indicating a generation rule (hereinafter also referred to as a first generation rule) of the operation plan corresponding to the learning device, thereby specifying a first generation rule corresponding to each of the one or more devices. Then, the control device 1 generates an operation plan (hereinafter also referred to as a first operation plan) corresponding to the one or more devices based on, for example, each of the specified first generation rules. Note that the learning device is, for example, one or more devices different from the one or more devices that generate the operation plan (for example, one or more devices provided in a plant different from the one or more devices that generate the operation plan).

[0016] As a result, the control device 1 in this embodiment can automatically and easily generate an operation plan corresponding to one or more devices for which the operation plan is to be generated, for example, by using the generated learning model. Therefore, the control device 1 can reduce the workload of an operator involved in generating an operation plan, for example.

[0017] In addition, the control device 1 in this embodiment, for example, by automatically generating an operation plan, makes it possible to prevent human errors such as failure to create or update an operation plan, compared to when an operator manually generates an operation plan.

[0018] [Hardware configuration of control device 1] Next, a description will be given of the hardware configuration of the control device 1. Fig. 2 is a diagram illustrating the hardware configuration of the control device 1 in the first embodiment.

[0019] The control device 1 is, for example, an electronic device having an electronic circuit. Specifically, as shown in Fig. 2, the control device 1 is, for example, a computer device having a CPU (Central Computing Unit) 101, which is a processor, a memory 102, a communication device 103, and a storage medium 104. Each part is connected to each other via, for example, a bus 105.

[0020] The storage medium 104 has, for example, a program storage area (not shown) that stores a program 110 for performing the driving plan generation process. The storage medium 104 also has, for example, a storage unit 130 (hereinafter also referred to as information storage area 130) that stores information used when performing the driving plan generation process. The storage medium 104 may be, for example, a hard disk drive (HDD) or a solid state drive (SSD).

[0021] The CPU 101 performs the driving plan generation process by, for example, executing a program 110 loaded from the storage medium 104 to the memory 102 .

[0022] The communication device 103 accesses the operation terminal 5 via a network NW such as the Internet.

[0023] The electronic circuit of the control device 1 may be, for example, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The operation plan generation process may be executed in, for example, the FPGA or the ASIC.

[0024] [Function of control device 1] Next, a description will be given of the functions of the control device 1. Fig. 3 is a block diagram of the functions of the control device 1 in the first embodiment. Fig. 4 is a block diagram of information stored in the information storage area 130 in the first embodiment.

[0025] As shown in FIG. 3, the control device 1 realizes various functions including an information receiving unit 111, an information management unit 112, an equipment information generation unit 113, an information identification unit 114, a generation rule prediction unit 115, an operation plan generation unit 116, an operation plan output unit 117, and a model learning unit 118 by organic cooperation between hardware such as a CPU 101 and a memory 102 and programs.

[0026] 4, the control device 1 stores, for example, equipment standard information 131, operation plan rule information 132, connection point information 133, facility information 141, equipment parent-child information 142, operation plan information 151, and learning model MD in the information storage area 130. Specifically, the equipment standard information 131 includes, for example, type parent-child information 131a and type detailed information 131b. Furthermore, the facility information 141 includes, for example, equipment list information 141a and connection list information 141b.

[0027] In the following, the operation plan generation system 1000 will be described as having one control device 1, but is not limited thereto. Specifically, the operation plan generation system 1000 may have, for example, a plurality of control devices 1. In this case, the plurality of control devices 1 may perform, for example, each process in a distributed manner.

[0028] First, the function of the process (hereinafter also referred to as information preparation process) of associating necessary information with device standard information 131 will be described. The following description will be given on the assumption that device standard information 131 is pre-stored in information storage area 130. Device standard information 131 is information including attributes, symbols, etc. for each type of device (hereinafter also referred to as class).

[0029] The information receiving unit 111 receives, for example, the operation plan rule information 132 input by the worker via the operation terminal 5. The operation plan rule information 132 is, for example, information for each type of equipment, and is information indicating a generation rule of the operation plan information 151 for the equipment corresponding to each type. Specifically, the operation plan rule information 132 is, for example, information generated based on standard operation plan information for each equipment, and is information including a variable (hereinafter also simply referred to as a variable) consisting of a conversion rule enclosed by "%" before and after. Then, the information management unit 112 stores, for example, the operation plan rule information 132 received by the information receiving unit 111 in the information storage area 130. Note that, for example, a plurality of operation plan rule information 132 may exist for each type. That is, the operation plan rule information 132 may exist for each unit that further subdivides the equipment type.

[0030] Furthermore, the information receiving unit 111 receives connection point information 133 input by the worker via the operation terminal 5, for example. The connection point information 133 is, for example, information for each type of device, and is information indicating attributes of connection points between the device corresponding to the type and other devices. That is, the connection point information 133 is, for example, information indicating attributes used to search for (identify) other devices located upstream or downstream of the device corresponding to the type. Then, the information management unit 112 stores the connection point information 133 received by the information receiving unit 111 in the information storage area 130, for example.

[0031] 4, the information management unit 112 associates the operation plan rule information 132 and the connection point information 133 corresponding to each type of equipment with the information for each type of equipment included in the equipment standard information 131 stored in the information storage area 130. Note that the following description will be given assuming that the operation plan rule information 132 and the connection point information 133 are included in the equipment standard information 131. That is, hereinafter, the equipment standard information 131, the operation plan rule information 132, and the connection point information 133 are collectively referred to simply as equipment standard information 131.

[0032] Next, functions in the process of generating a learning model for estimating the operation plan rule information 132 corresponding to each device (hereinafter, also referred to as model learning process) will be described.

[0033] The model learning unit 118 generates a learning model by performing machine learning on teacher data including, for example, device standard information 131 corresponding to the learning device and facility information 141 corresponding to the learning device.

[0034] Specifically, the model learning unit 118 generates a learning model by performing machine learning of teacher data including information generated using at least one of connection point information 133 corresponding to the type of learning device, device list information 141a corresponding to the learning device, connection list information 141b corresponding to the learning device, and device parent-child information 142 corresponding to the learning device, and information indicating driving plan rule information 132 corresponding to the learning device. Then, the information management unit 112 stores the generated learning model in the information storage area 130, for example.

[0035] Next, functions in the process of generating facility information 141 (hereinafter also referred to as facility information generation process) will be described.

[0036] The equipment information generation unit 113 receives, for example, specification by an operator of information indicating one or more devices and information indicating the connection relationships between the one or more devices on a generation screen (not shown) displayed on the operation terminal 5.

[0037] Specifically, the facility information generating unit 113 accepts, for example, on a generated screen prepared in advance, designation of symbols corresponding to the types of each device (i.e., icons corresponding to the types of each device) and attributes of the symbols corresponding to the types of each device. In this case, the facility information generating unit 113 also accepts, for example, designation of information indicating the connection relationships of each symbol.

[0038] Then, the facility information generation unit 113 generates facility information 141 from each piece of information specified via, for example, the generation screen. Specifically, the facility information generation unit 113 generates, for example, from each piece of information specified via the generation screen, device list information 141a which is information about each device included in the facility information 141, and connection list information 141b which is information about the connection state of each device included in the facility information 141. Thereafter, the information management unit 112 stores the facility information 141 generated by the facility information generation unit 113 in the information storage area 130, for example.

[0039] Furthermore, the equipment information generating unit 113 accepts, for example, designation of information indicating the parent-child relationship of one or more pieces of equipment designated by the worker on a generation screen. Then, the equipment information generating unit 113 generates equipment parent-child information 142 indicating the parent-child relationship of each piece of equipment included in the equipment information 141 from each piece of information designated via the generation screen. Thereafter, the information managing unit 112 stores, for example, the equipment parent-child information 142 generated by the equipment information generating unit 113 in the information storage area 130. Note that, hereinafter, the description will be given assuming that the equipment parent-child information 142 is included in the equipment information 141. That is, hereinafter, the equipment information 141 and the equipment parent-child information 142 will be collectively referred to simply as equipment information 141.

[0040] Next, functions in the process of generating the driving plan information 151 (hereinafter, also referred to as driving plan generation main process) will be described.

[0041] The information identification unit 114, for example, refers to the equipment standard information 131 stored in the information storage area 130, and identifies, for each of one or more pieces of equipment included in the equipment information 141 generated by the equipment information generation unit 113, the equipment standard information 131 (first equipment standard information 131) corresponding to the type (first type) in which each piece of equipment is included.

[0042] Specifically, the information identifying unit 114, for example, refers to type parent-child information 131a included in the device standard information 131 stored in the information storage area 130, and identifies the type of each device for each of the one or more devices included in the facility information 141. The type parent-child information 131a is, for example, information indicating a parent-child relationship by type, and a type corresponding to a child inherits the attributes of the type corresponding to a parent.

[0043] The generation rule prediction unit 115, for example, by using the learning model MD stored in the information storage area 130, identifies, for each of one or more pieces of equipment included in the equipment information 141 stored in the information storage area 130, operation plan rule information 132 corresponding to each piece of equipment from the operation plan rule information 132 included in the equipment standard information 131 stored in the information storage area 130 (hereinafter also referred to as the first operation plan rule information 132).

[0044] Specifically, the generation rule prediction unit 115 inputs, for example, for each of one or more devices included in the facility information 141, information generated using at least one of the connection point information 133 corresponding to the type of each device, the device list information 141a corresponding to each device, the connection list information 141b corresponding to each device, and the device parent-child information 142 corresponding to each device into the learning model. Then, the generation rule prediction unit 115 identifies, for example, the first operation plan rule information 132 indicated by the information output from the learning model MD.

[0045] More specifically, the generation rule prediction unit 115, for example, identifies driving plan rule information 132 included in the first equipment standard information 131 corresponding to each equipment as the first driving plan rule information 132 corresponding to each equipment, where a value indicating the likelihood that the driving plan rule information 132 is the first driving plan rule information 132 corresponding to each equipment (a value output by the learning model MD) is equal to or greater than a threshold value.

[0046] The operation plan generation unit 116 generates operation plan information 151 corresponding to each of one or more pieces of equipment included in the equipment information 141 based on, for example, each of the first operation plan rule information 132 identified by the generation rule prediction unit 115.

[0047] Specifically, for example, when a variable exists in the driving plan rule information 132 corresponding to each device, the driving plan generating unit 116 refers to at least one of the connection point information 133, the device list information 141a, the connection list information 141b, and the device parent-child information 142 to identify a device (hereinafter also referred to as a first device) corresponding to the variable for each of one or more devices included in the equipment information 141. After that, the driving plan generating unit 116 generates driving plan information 151 corresponding to one or more devices by associating the first device corresponding to each device with the variable corresponding to each device for each of one or more devices included in the equipment information 141.

[0048] In other words, the operation plan generation unit 116 generates operation plan information 151 corresponding to one or more pieces of equipment by, for example, converting variables in the operation plan rule information 132 corresponding to each piece of equipment into information indicating a first piece of equipment corresponding to each piece of equipment (e.g., the name of the first piece of equipment), for each piece of equipment included in the equipment information 141.

[0049] The driving plan rule information 132 may include a program (hereinafter also referred to as an expansion program) that automatically generates the driving plan information 151 from the driving plan rule information 132 by referring to at least one of the connection point information 133, the device list information 141a, the connection list information 141b, and the device parent-child information 142. The driving plan generating unit 116 may generate the driving plan information 151 by executing the expansion program, for example.

[0050] The driving plan output unit 117 outputs, for example, the driving plan information 151 generated by the driving plan generating unit 116. Specifically, the driving plan output unit 117 outputs the driving plan information 151 to the operation terminal 5, for example.

[0051] [Operation plan generation process in the first embodiment] Next, the operation plan generation process in the first embodiment will be described. Figures 5 to 8 are flow charts for explaining the operation plan generation process in the first embodiment. Figures 9 to 29 are diagrams for explaining the details of the operation plan generation process in the first embodiment.

[0052] In the following description, the equipment standard information 131 is assumed to be information for each type of equipment managed by an intelligent P&ID (Intelligent Piping & Instrument Diagram). In the following description, the equipment information generating unit 113 is assumed to be a function that generates equipment information 141 using the function of the intelligent P&ID.

[0053] [Information preparation processing] First, the information preparation process in the driving plan generation process will be described with reference to FIG 5. The information preparation process in the first embodiment will be described with reference to the flowchart shown in FIG 5.

[0054] As shown in FIG. 5, the information management unit 112, for example, associates information for each type of equipment contained in the equipment standard information 131 stored in the information storage area 130 with operation plan rule information 132 corresponding to each type (step S1 in FIG. 5).

[0055] Furthermore, the information management unit 112 further associates connection point information 133 corresponding to each type of equipment with information for each type of equipment included in the equipment standard information 131 stored in the information storage area 130 (step S2 in FIG. 5). That is, steps S1 and S2 are processes for adding information for automatically generating operation plan information 151 to the equipment standard information 131 in the intelligent P&ID. Specific examples of the equipment standard information 131 will be described below.

[0056] [Specific examples of Equipment Standard Information 131] 9 to 12 are diagrams for explaining a specific example of the equipment standard information 131. Specifically, FIG. 9 is a diagram for explaining a specific example of the type parent-child information 131a. Also, FIG. 10 is a diagram for explaining information on the type of equipment in the type detailed information 131b (hereinafter, also referred to as equipment type information 131b1). Also, FIG. 11 is a diagram for explaining information on the type of connection between equipment in the type detailed information 131b (hereinafter, also referred to as connection type information 131b2). Also, FIG. 12 is a diagram for explaining a specific example of the equipment type information 131b1 after the operation plan rule information 132 and the connection point information 133 are associated in steps S1 and S2. Also, FIG. 13 is a diagram for explaining a specific example of a symbol in the intelligent P&ID.

[0057] In addition, the equipment standard information 131, the operation plan rule information 132, and the connection point information 133 may be generated, for example, for each plant for which the operation plan information 151 is to be generated (for example, for multiple plants such as a water treatment plant, a power generation plant, and a chemical plant).

[0058] [Example of type parent-child information 131a] First, a specific example of the type parent-child information 131a will be described.

[0059] The type parent-child information 131a shown in Fig. 9 indicates, for example, that a "volute pump", a "submersible pump", a "single-shaft eccentric screw pump", etc. belong to the "pump" category. In other words, the type parent-child information 131a shown in Fig. 9 indicates that a parent-child relationship is established in which a "pump" is the parent type and a "volute pump", a "submersible pump", a "single-shaft eccentric screw pump", etc. are child types, and that the child types, a "volute pump", a "submersible pump", a "single-shaft eccentric screw pump", etc., inherit the attributes of the parent type, "pump".

[0060] 9 indicates that, for example, a "level meter (electrode rod type)", a "level meter (paddle type)", a "level meter (phototube type)", etc. belong to the "level meter". That is, the type parent-child information 131a shown in Fig. 9 indicates that a parent-child relationship is established in which a "level meter" is the parent type and "level meter (electrode rod type)", "level meter (paddle type)", and "level meter (phototube type)" are the child types, and that the child types "level meter (electrode rod type)", "level meter (paddle type)", and "level meter (phototube type)" etc. inherit the attributes of the parent type "level meter".

[0061] [Specific example (1) of device type information 131b1] Next, a specific example of the device type information 131b1 will be described.

[0062] The device type information 131b1 shown in Fig. 10 has, for example, items such as "type" in which the type is set, "parent type" in which the type corresponding to the parent of the type is set, "attribute item" in which the item of the attribute of the device corresponding to the type is set, and "symbol" in which the identification information of the symbol corresponding to the type to which each device belongs is set. In the "attribute item", for example, the name of each device, the identification information of each device, the number of each device, information indicating the manufacturer of each device, and information indicating the model of each device are set. That is, the "parent type" column in Fig. 10 represents the contents described in Fig. 9 in table format. In the following description, it is assumed that "-" is set to items for which no information is set.

[0063] Specifically, in the device type information 131b1 shown in FIG. 10, the information in the first row has, for example, “Pump” set as the “Type”, “-” set as the “Parent Type”, “A1” set as the “Attribute Item”, and “C011” set as the “Symbol”.

[0064] In addition, in the device type information 131b1 shown in FIG. 10, in the information on the second line, for example, “Type” is set to “Centrifugal Pump”, “Parent Type” is set to “Pump”, “Attribute Item” is set to “A11”, and “Symbol” is set to “C012”.

[0065] 10, in the information on the third line, for example, "submersible pump" is set as the "type", "pump" is set as the "parent type", "A12" is set as the "attribute item", and "C013" is set as the "symbol". Explanation of other information included in FIG. 10 will be omitted.

[0066] [Specific example of connection type information 131b2] Next, a specific example of the connection type information 131b2 will be described.

[0067] 11 has items such as "type" in which a type of connection device such as piping or wiring (hereinafter also referred to as connection device) is set, "parent type" in which a type corresponding to the parent of the type is set, "attribute item" in which an item of the attribute of the connection device corresponding to the type is set, and "symbol" in which identification information of the symbol corresponding to the type to which each device belongs is set. In the "attribute item", for example, the identification information of each connection device, the type of each connection device, the material of each connection device, the size of each connection device, etc. are set.

[0068] Specifically, in the connection type information 131b2 shown in FIG. 11, the information in the first row has, for example, “Pipe” set as the “Type”, “-” set as the “Parent Type”, “C1” set as the “Attribute Item”, and “C031” set as the “Symbol”.

[0069] 11, in the information on the second line, for example, "wiring" is set as the "type", "-" is set as the "parent type", "D1" is set as the "attribute item", and "C041" is set as the "symbol". Explanation of other information included in FIG. 11 will be omitted.

[0070] [Specific example (2) of device type information 131b1] Next, another specific example of the device type information 131b1 will be described. Specifically, a specific example of the device type information 131b1 after the operation plan rule information 132 and the connection point information 133 are associated with each other in steps S1 and S2 will be described.

[0071] The device type information 131b1 shown in Figure 12 has, in addition to each item described in Figure 10, the following items: "driving plan rule information" in which identification information of the driving plan rule information 132 associated in step S1 is set, and "connection point information" in which the content of the connection point information 133 associated in step S2 is set.

[0072] Specifically, in the device type information 131b1 shown in Fig. 12, for example, "pump" is set as the "type", "-" is set as the "parent type", "A1" is set as the "attribute item", "C011" is set as the "symbol", and "132a" is set as the "operation plan rule information". In addition, in the device type information 131b1 shown in Fig. 12, for example, as the "connection point information", "first connection point: upstream" indicating that the first connection point (hereinafter also referred to as the first connection point) of the device whose "type" is "pump" is a connection point connecting to another device located upstream, and "second connection point: downstream" indicating that the second connection point (hereinafter also referred to as the second connection point) of the device whose "type" is "pump" is a connection point connecting to another device located downstream are set.

[0073] That is, the equipment type information 131b1 shown in FIG. 12 indicates, for example, that the “attribute item” corresponding to the pump is “A1”, the “symbol” corresponding to the pump is “C011”, the “operation plan rule information” corresponding to the pump is “132a”, and the “connection point information” corresponding to the pump is “first connection point: upstream” and “second connection point: downstream”.

[0074] 12, the information in the second line has, for example, "volute pump" set as the "type", "pump" set as the "parent type", "A11" set as the "attribute item", "C012" set as the "symbol", and "-" set as the "operation plan rule information". Also, in the equipment type information 131b1 shown in Fig. 12, the information in the second line has, for example, "connection point information" set as "third connection point: sealwater" indicating that the third connection point (hereinafter also referred to as the third connection point) of the equipment whose "type" is "volute pump" is a connection point that connects to a pipe (not shown) for injecting shaft seal water.

[0075] Here, the type parent-child information 131a shown in Fig. 9 indicates, for example, that "volute pump" is a type corresponding to a child of "pump". Therefore, for example, the information in the first row (information about "pump") in the device type information 131b1 shown in Fig. 12 is inherited by the "volute pump". That is, the device type information 131b1 shown in Fig. 12 indicates, for example, that the "operation plan rule information" corresponding to the volute pump is "132a", and that the "connection point information" corresponding to the volute pump is "first connection point: upstream", "second connection point: downstream", and "third connection point: sealwater".

[0076] 12, the information in the third row has, for example, "submersible pump" set as the "type", "pump" set as the "parent type", "A12" set as the "attribute item", "C013" set as the "symbol", and "-" set as the "operation plan rule information". Also, in the device type information 131b1 shown in FIG. 10, the information in the third row has, for example, "-" set as the "connection point information".

[0077] Here, the type parent-child information 131a shown in FIG. 9 indicates, for example, that "submersible pump" is a type that corresponds to a child of "pump". Therefore, for example, the information in the first row (information about "pump") in the device type information 131b1 shown in FIG. 12 is inherited by "submersible pump". That is, the device type information 131b1 shown in FIG. 12 indicates, for example, that the "operation plan rule information" corresponding to the submersible pump is "132a", and that the "connection point information" corresponding to the submersible pump is "first connection point: upstream" and "second connection point: downstream". Description of other information included in FIG. 12 will be omitted.

[0078] [Examples of symbols in Intelligent P&ID] Next, a specific example of the symbol in the intelligent P&ID will be described. Specifically, Fig. 13 is a diagram for explaining the symbol S corresponding to the centrifugal pump in the equipment type information 131b1 (the equipment type information 131b1 after the operation plan rule information 132 and the connection point information 133 are associated with each other) described in Fig. 12.

[0079] Specifically, the device type information 131b1 (connection point information 133) described in FIG. 12 indicates, for example, that the connection points corresponding to a volute pump are “first connection point: upstream,” “second connection point: downstream,” and “third connection point: sealwater.”

[0080] Therefore, as shown in FIG. 13, the symbol S corresponding to a volute pump is associated with, for example, information indicating that the connection attribute corresponding to the first connection point (the connection point on the left side in FIG. 13) is "upstream", information indicating that the connection attribute corresponding to the second connection point (the connection point on the right side in FIG. 13) is "downstream", and information indicating that the connection attribute corresponding to the third connection point (the connection point on the top side in FIG. 13) is "sealwater".

[0081] [Specific example of operation plan rule information 132] Next, a specific example of the operation plan rule information 132 will be described. FIG. 14 and FIG. 15 are diagrams for explaining a specific example of the operation plan rule information 132. Specifically, FIG. 14 is a diagram for explaining a specific example of the operation plan rule information 132 (hereinafter also referred to as operation plan rule information 132a) corresponding to each device whose type is a pump. Also, FIG. 15 is a diagram for explaining a specific example of the operation plan rule information 132 (hereinafter also referred to as operation plan rule information 132b) corresponding to each device whose type is a level gauge. Below, a case where there is one operation plan rule information 132 corresponding to each type will be described. Note that a specific example where there are multiple operation plan rule information 132 corresponding to each type will be described later.

[0082] Conversion rules included in variables in the operation plan rule information 132 shown in Fig. 14 and the like include, for example, "Me" indicating an appliance to be controlled, "Parent" indicating an appliance that is the parent of the appliance to be controlled in the parent-child relationship, "Upstream" indicating an appliance arranged upstream of the appliance to be controlled, "Downstream" indicating an appliance arranged downstream of the appliance to be controlled, etc. In addition, conversion rules included in variables in the operation plan rule information 132 shown in Fig. 14 and the like include, for example, "Pump" indicating an appliance whose type is a pump, "Switch" indicating an appliance whose type is a switch, "Ls" indicating an appliance whose type is a level gauge, "Ts" indicating an appliance whose type is a thermometer, etc. In addition, the conversion rules included in the variables in the operation plan rule information 132 shown in Figure 14 etc. include, for example, "Run" indicating the operating state of the equipment, "H" indicating that the measurement value of the equipment is equal to or greater than the first upper threshold, "HH" indicating that the measurement value of the equipment is equal to or greater than a second upper threshold which is greater than the first upper threshold, "L" indicating that the measurement value of the equipment is equal to or less than the first lower threshold, "LL" indicating that the measurement value of the equipment is equal to or less than a second lower threshold which is smaller than the first lower threshold, and "from H to L" indicating that the measurement value of the equipment has transitioned from equal to or greater than the first upper threshold to the first lower threshold.

[0083] Specifically, the operation plan rule information 132a shown in FIG. 14 indicates that an independent operation circuit is provided that outputs an operation signal in response to inputs of, for example, a mode signal, an operation signal, an automatic operation signal, and an interlock signal. The mode signal is a signal output from a mode switch, which indicates "automatic" or "manual." The operation signal is a signal output from an operation switch, which indicates "operation" or "stop." The automatic operation signal is expressed as "%Me%.automatic operation command" and indicates an automatic operation command for the pump to be controlled. The interlock signal is expressed as "%Upstream.Ls%.LL" and indicates that a level gauge installed in an equipment upstream of the pump to be controlled has fallen below the second lower limit threshold.

[0084] In addition, the operation plan rule information 132a shown in FIG. 14 indicates that an AND circuit is provided that inputs, for example, what is expressed as "%Me%. automatic mode", what is expressed as "%Upstream.Ls%.H to L", and what is expressed as "%Downstream.Ls%.H", and outputs what is expressed as "%Me%. automatic operation command". "%Me%. automatic mode" indicates that the mode signal in the controlled object is "automatic". Furthermore, "%Upstream.Ls%.H to L" indicates that the value of the level meter installed in the device upstream of the controlled object has transitioned from the first upper limit threshold or more to the first lower limit threshold. Furthermore, "%Downstream.Ls%.H" indicates that the value of the level meter installed in the device downstream of the device has transitioned to the first lower limit threshold or less.

[0085] Also, the operation plan rule information 132b shown in FIG. 15 indicates that a standard logic circuit is provided that inputs, for example, what is expressed as "%Me%" and outputs what is expressed as "%Parent.Name%.HH", what is expressed as "%Parent.Name%.H", what is expressed as "%Parent.Name%.L", what is expressed as "%Parent.Name%.LL", and what is expressed as "%Parent.Name%.H to L". "Me" indicates the measurement value of the controlled object. Also, "%Parent.Name%.HH" indicates that the water level of the device that is the parent of the controlled object in the parent-child relationship has reached or exceeded the second upper limit threshold. Also, "%Parent.Name%.H" indicates that the water level of the device that is the parent of the controlled object in the parent-child relationship has reached or exceeded the first upper limit threshold. Also, "%Parent.Name%.L" indicates that the water level of the device that is the parent of the controlled object in the parent-child relationship has reached or exceeded the first lower limit threshold. Additionally, "%Parent.Name%.LL" indicates that the water level of the device that is the parent of the controlled device in the parent-child relationship has fallen below the second lower threshold. Additionally, "%Parent.Name%.H to L" indicates that the water level of the device that is the parent of the controlled device in the parent-child relationship has transitioned from above the first upper threshold to the first lower threshold.

[0086] [Model generation process] Next, the model generation process of the operation plan generation process will be described with reference to Fig. 6. The model generation process in the first embodiment is shown in Fig. 6 as a flow chart.

[0087] As shown in FIG. 6, the model learning unit 118 generates teacher data DT (multiple teacher data DT) including information generated using at least one of connection point information 133 corresponding to the type of learning equipment, equipment list information 141a corresponding to the learning equipment, connection list information 141b corresponding to the learning equipment, and equipment parent-child information 142 corresponding to the learning equipment, and information indicating the driving plan rule information 132 corresponding to the learning equipment (step S101 in FIG. 6).

[0088] Specifically, as shown in FIG. 16, the operator inputs, for example, the connection point information 133 corresponding to the type of the learning device, the device list information 141a corresponding to the learning device, the connection list information 141b corresponding to the learning device, the device parent-child information 142 corresponding to the learning device, and information indicating the driving plan rule information 132 corresponding to the learning device (for example, the identification information of the driving plan rule information 132) to the control device 1. Then, the model learning unit 118 generates teacher data DT including, for example, information generated using at least one of the connection point information 133 corresponding to the type of the learning device, the device list information 141a corresponding to the learning device, the connection list information 141b corresponding to the learning device, and the device parent-child information 142 corresponding to the learning device, and information indicating the driving plan rule information 132 corresponding to the learning device. After that, the information management unit 112 stores, for example, the generated teacher data DT in the information storage area 130.

[0089] For example, the worker may input the generated teacher data DT to the control device 1. Then, the information management unit 112 may store the input generated teacher data DT in the information storage area 130. A specific example of the teacher data DT will be described below.

[0090] [Specific examples of teacher data DT] Figures 27 to 29 are diagrams for explaining specific examples of the teacher data DT. Each of Figures 27 to 29 is a specific example of one of a plurality of teacher data DT used for learning the learning model MD.

[0091] The teacher data DT shown in FIG. 27 and the like has, for example, items such as a "parent-child connection vector" in which a vector indicating the parent-child relationship and connection relationship of each device identified from the connection point information 133 corresponding to the type of each device, the connection list information 141b corresponding to each device, and the device parent-child information 142 corresponding to each device is set, a "type vector" in which a vector indicating the type of each device identified from the device list information 141a corresponding to each device is set, and a "name vector" in which a vector indicating the name of each device identified from the device list information 141a corresponding to each device is set. In addition, the teacher data DT shown in FIG. 27 and the like has, for example, items such as a "number" in which the number of each device identified from the device list information 141a corresponding to each device is set, and a "driving plan rule information" in which the identification information of the driving plan rule information 132 corresponding to each device is set.

[0092] Specifically, in the "parent-child connection vector" in the teacher data DT shown in Fig. 27 etc., for example, a vector indicating the parent-child relationship between each device and other devices (hereinafter also referred to as the first vector) is set. Specifically, in the "parent-child connection vector", for example, the first value is set to "1" which is the first vector corresponding to other devices that are the parents of each device, or "0" which is the first vector corresponding to devices other than other devices that are the parents of each device.

[0093] In addition, in the "parent-child connection vector" in the teacher data DT shown in FIG. 27 and the like, for example, a two-dimensional vector (hereinafter also referred to as a second vector) indicating the connection relationship between each device and other devices (for example, the placement position of other devices when the placement position of each device is used as a reference) is set. Specifically, in the "parent-child connection vector", for example, the second and third values ​​are set to "1, 0" which is a second vector corresponding to other devices connected to each device at the upstream connection point (upstream) of each device, "-1, 0" which is a second vector corresponding to other devices connected to each device at the downstream connection point (downstream) of each device, and "0, 1" which is a second vector corresponding to other devices connected to each device at the other connection point of each device. The other connection points are, for example, connection points (sealwater, etc.) other than the upstream and downstream connection points of each device.

[0094] In addition, in the "type vector" in the teacher data DT shown in FIG. 27 and the like, for example, a vector indicating the type of each device is set. Specifically, in the "type vector", for example, "Km" indicating a pump, which is a type of transfer pump, is set. In addition, in the "type vector", for example, "Kn1" indicating a water tank, which is a type of sludge storage tank, is set. In addition, in the "type vector", for example, "Kn2" indicating a hopper, which is a type of sludge hopper, is set. In addition, in the "type vector", for example, "Kn3" indicating a level gauge, which is a type of sludge storage tank level gauge or sludge hopper level gauge, is set.

[0095] In addition, in the "name vector" in the teacher data DT shown in FIG. 27 and the like, for example, a vector indicating the name of each device is set. Specifically, in the "name vector", for example, "Nm" indicating the name of a transfer pump is set. In addition, in the "name vector", for example, "Nn1" indicating the name of a sludge storage tank is set. In addition, in the "name vector", for example, "Nn2" indicating the name of a sludge hopper is set. In addition, in the "name vector", for example, "Nn3" indicating the name of a sludge storage tank level gauge is set. In addition, in the "name vector", for example, "Nn4" indicating the name of a sludge hopper level gauge is set.

[0096] More specifically, in the teacher data DT shown in FIG. 27, for example, in the first row, "0" is set as the first vector in the "parent-child connection vector", "0,0" is set as the second vector in the "parent-child connection vector", "Km" is set as the "type vector", "Nm" is set as the "name vector", and "1" is set as the "number of vehicles". Also, in the teacher data DT shown in FIG. 27, for example, in the second row, "0" is set as the first vector in the "parent-child connection vector", "-1,0" is set as the second vector in the "parent-child connection vector", "Kn1" is set as the "type vector", "Nn1" is set as the "name vector", and "1" is set as the "number of vehicles". Also, in the teacher data DT shown in FIG. 27, for example, in the third row, "0" is set as the first vector in the "parent-child connection vector", "1,0" is set as the second vector in the "parent-child connection vector", "Kn2" is set as the "type vector", "Nn2" is set as the "name vector", and "1" is set as the "number of vehicles". Furthermore, in the teacher data DT shown in FIG. 27, for example, "132c" indicating the driving plan rule information 132c (described later) shown in FIG. 22 and FIG. 23 is set as the "driving plan rule information".

[0097] In addition, in the teacher data DT shown in Fig. 28, for example, in the first row, "0" is set as the first vector in the "parent-child connection vector", "0,0" is set as the second vector in the "parent-child connection vector", "Km" is set as the "type vector", "Nm" is set as the "name vector", and "2" is set as the "number of vehicles". Furthermore, in the teacher data DT shown in Fig. 28, for example, "L11" indicating the part (described later) included in the equipment symbol L11 shown in Fig. 23 is set as the "operation plan rule information".

[0098] In addition, in the teacher data DT shown in Fig. 29, for example, in the first row, "0" is set as the first vector in the "parent-child connection vector", "0,0" is set as the second vector in the "parent-child connection vector", "Km" is set as the "type vector", "Nm" is set as the "name vector", and "3" is set as the "number of vehicles". Furthermore, in the teacher data DT shown in Fig. 29, for example, "L12" indicating the part (described later) included in the equipment symbol L12 shown in Fig. 23 is set as the "operation plan rule information".

[0099] In the example shown in FIG. 27 etc., each of the connection point information 133, the device list information 141a, the connection list information 141b and the device parent-child information 142 may be converted into a vector (numeric value) by using, for example, Word2Vec or the like.

[0100] 27 and other examples have been described in which the teacher data DT includes vectors identified from the connection point information 133, the device list information 141a, the connection list information 141b, and the device parent-child information 142, but this is not limiting. Specifically, the teacher data DT may include, for example, information included in the connection point information 133, the device list information 141a, the connection list information 141b, and the device parent-child information 142 as is.

[0101] Returning to FIG. 6, the model learning unit 118 generates a learning model MD by performing machine learning on the teacher data DT (plurality of teacher data DT) generated in step S101 (step S102 in FIG. 6).

[0102] Specifically, the model learning unit 118 generates the learning model MD by using the teacher data DT stored in the information storage area 130, for example, as shown in FIG.

[0103] That is, the model learning unit 118 generates a learning model MD capable of identifying the first operation plan rule information 132 suitable for generating the operation plan information 151 corresponding to each device included in the facility information 141, for example.

[0104] As a result, the control device 1 in this embodiment can automatically and easily generate the operation plan information 151 corresponding to each device by using, for example, the learning model MD. Therefore, the control device 1 can reduce the workload of an operator involved in generating the operation plan information 151, for example.

[0105] [Facility information generation process] Next, the facility information generation process of the operation plan generation process will be described with reference to Fig. 7. The facility information generation process in the first embodiment will be described with reference to a flow chart.

[0106] As shown in FIG. 7, for example, the equipment information generation unit 113 accepts, on a generation screen, the operator's specification of one or more symbols (for example, dragging and dropping each symbol from a list not shown) and specification of attributes of the one or more symbols (step S11 in FIG. 7).

[0107] Specifically, the attributes of one or more symbols are substantial information corresponding to, for example, the "attribute item" of the equipment type information 131b1 described in Fig. 10. Specifically, the attributes of one or more symbols are, for example, the name of each equipment, the identification information of each equipment, the number of each equipment, information indicating the manufacturer of each equipment, and information indicating the model of each equipment. Therefore, for example, if the "attribute item" corresponding to the type including each symbol is "equipment name," the worker specifies, as the attribute of each symbol, the name of the equipment represented by each symbol, such as "transfer pump."

[0108] That is, in step S11, the worker specifies each symbol and also specifies the attributes of each symbol, thereby making the device represented by each symbol identifiable from other devices.

[0109] Furthermore, the facility information generating unit 113 receives, for example, a specification by an operator of information indicating a connection relationship between one or more symbols on a generation screen displayed on the operation terminal 5 (step S12 in FIG. 7).

[0110] Then, the facility information generation unit 113 generates facility information 141 from each piece of information specified in steps S11 and S12, for example. Then, the information management unit 112 stores the generated facility information 141 in the information storage area 130, for example.

[0111] Furthermore, the facility information generating unit 113 receives, for example, designation of information indicating a parent-child relationship between one or more symbols designated by the worker on the generation screen (step S13 in FIG. 7).

[0112] Then, in step S13, the facility information generation unit 113 generates the device parent-child information 142 from the information specified via the generation screen, for example. After that, the information management unit 112 stores the generated device parent-child information 142 in the information storage area 130, for example. Specific examples of the facility information 141 and the device parent-child information 142 will be described below.

[0113] [Example of Facility Information 141 (1)] First, a description will be given of a specific example of the facility information 141. Fig. 17 to Fig. 19 are diagrams for explaining a specific example of the facility information 141.

[0114] Note that steps S11 and S12 can be realized by normal design work using, for example, an intelligent P&ID. Specifically, Fig. 17 is a flow diagram of a facility created using an intelligent P&ID.

[0115] The equipment information 141 shown in Fig. 17 includes, for example, information on a sludge storage tank OB1, a transfer pump OB2, and a sludge hopper OB3. Specifically, the equipment information 141 shown in Fig. 17 indicates, for example, that the sludge storage tank OB1 and the transfer pump OB2 are connected. The equipment information 141 shown in Fig. 17 also indicates, for example, that the transfer pump OB2 and the sludge hopper OB3 are connected. The equipment information 141 shown in Fig. 17 also indicates, for example, that a level gauge OB11 (hereinafter also referred to as a sludge storage tank level gauge OB11) is attached to the sludge storage tank OB1, and that a level gauge OB31 (hereinafter also referred to as a sludge hopper level gauge OB31) is attached to the sludge hopper OB3.

[0116] [Example of Facility Information 141 (2)] Next, a specific example of the facility information 141 will be described. Fig. 18 and Fig. 19 are diagrams for explaining a specific example of the facility information 141. Specifically, Fig. 18 is a diagram for explaining a specific example of the device list information 141a of the facility information 141 explained in Fig. 17 expressed in a table format. Also, Fig. 19 is a diagram for explaining a specific example of the connection list information 141b of the facility information 141 explained in Fig. 17 expressed in a table format. Note that the following description will be given on the assumption that each device is included in a group of other devices (hereinafter also referred to as a device group) that corresponds to the parent of each device.

[0117] First, a specific example of the device list information 141a will be described.

[0118] The device list information 141a shown in FIG. 18 has, for example, items such as "type" in which the type of each device is set, "device name" in which the name of each device is set, "attribute" in which the attribute of each device (the attribute specified in step S11 in FIG. 7) is set, and "device group" in which the device group to which each device is included is set.

[0119] Specifically, in the equipment list information 141a shown in FIG. 18, in the information in the first line, for example, “Type” is set to “Centrifugal Pump”, “Equipment Name” is set to “Transfer Pump”, and “Equipment Group” is set to “Wastewater Treatment Facility”.

[0120] 18, in the information on the second line, for example, "Level meter (electrode rod type)" is set as "Type", "Sludge storage tank level meter" is set as "Device name", and "Sludge storage tank" is set as "Device group". Explanation of other information included in FIG. 18 will be omitted.

[0121] Next, a specific example of the connection list information 141b will be described.

[0122] The connection list information 141b shown in FIG. 19 has, for example, items such as “Type” in which the type of each connected device is set, “Device Name 1. Connection Point” in which the name of the first device connected by each connected device and the connection point of the first device are set, “Device Name 2. Connection Point” in which the name of the second device connected by each connected device and the connection point of the second device are set, and “Connection Attributes” in which the attributes of each connected device are set.

[0123] Specifically, in the connection list information 141b shown in FIG. 19, the information in the first line has, for example, "Pipe" set as "Type," "Transfer pump.Connection point 1" set as "Equipment name 1.Connection point," and "Sludge storage tank.Connection point 2" set as "Equipment name 2.Connection point."

[0124] 19, in the information on the second line, for example, "piping" is set as "type," "sludge hopper.connection point 1" is set as "device name 1.connection point," and "transfer pump.connection point 2" is set as "device name 2.connection point." Explanation of other information included in FIG. 19 will be omitted.

[0125] [Example of Device Parent-Child Information 142] Next, a description will be given of a specific example of the device parent-child information 142. FIG.

[0126] The equipment parent-child information 142 shown in Fig. 20 indicates, for example, that there are a "water intake facility," a "pretreatment facility," a "membrane filtration facility," a "chemical injection facility," a "water supply facility," and a "wastewater treatment facility" at one level below the "AA water purification plant." In other words, the equipment parent-child information 142 shown in Fig. 20 indicates that a parent-child relationship is established in which the "AA water purification plant" is the parent and the "water intake facility," "pretreatment facility," "membrane filtration facility," "chemical injection facility," "water supply facility," and "wastewater treatment facility" are the children.

[0127] 20 indicates that, for example, a "sludge storage tank," a "transfer pump," and a "sludge hopper" exist in the hierarchy one level below the "wastewater treatment facility." In other words, the equipment parent-child information 142 shown in Fig. 20 indicates that a parent-child relationship is established in which the "wastewater treatment facility" is the parent and the "sludge storage tank," "transfer pump," and "sludge hopper" are the children.

[0128] Also, the device parent-child information 142 shown in Fig. 20 indicates, for example, that a "sludge storage tank level meter" exists in the hierarchy one level below the "sludge storage tank." In other words, the device parent-child information 142 shown in Fig. 20 indicates, for example, that a parent-child relationship is established in which the "sludge storage tank" is the parent and the "sludge storage tank level meter" is the child.

[0129] Furthermore, the equipment parent-child information 142 shown in Fig. 20 indicates, for example, that a "sludge hopper level gauge" exists at one level below the "sludge hopper". In other words, the equipment parent-child information 142 shown in Fig. 20 indicates, for example, that a parent-child relationship is established in which the "sludge hopper" is the parent and the "sludge hopper level gauge" is the child. Descriptions of other information included in Fig. 20 will be omitted.

[0130] The device parent-child information 142 can be edited, for example, on a screen as shown in FIG. 20, and is stored in the "device group" column in the device list information 141a described with reference to FIG.

[0131] [Main process for generating driving plans] Next, the main process of generating an operation plan will be described with reference to Fig. 8. The main process of generating an operation plan in the first embodiment is shown in Fig. 8 as a flow chart.

[0132] The information identifying unit 114, for example, identifies one device included in the facility information 141 stored in the information storage area 130 (step S21 in FIG. 8). Specifically, the information identifying unit 114, for example, identifies one device included in the facility information 141 generated in the facility information generation process.

[0133] Then, the information identifying unit 114, for example, refers to type parent-child information 131a included in the device standard information 131 stored in the information storage area 130, and identifies the type to which the device identified in step S21 belongs (step S22 in FIG. 8).

[0134] Next, the information identifying unit 114, for example, refers to the device standard information 131 stored in the information storage area 130, and identifies the first device standard information 131 corresponding to the type identified in step S22 (step S23 in FIG. 8).

[0135] Then, the generation rule prediction unit 115, for example, by using the learning model MD stored in the information storage area 130, identifies the first driving plan rule information 132 corresponding to the equipment identified in step S21 from among the driving plan rule information 132 stored in the information storage area 130 (step S24 in FIG. 8).

[0136] Specifically, as shown in FIG. 21, the generation rule prediction unit 115 generates input data DT0 from at least one of the connection point information 133 corresponding to the first device standard information 131 identified in step S23, the device list information 141a corresponding to the device identified in step S21, the connection list information 141b corresponding to the device identified in step S21, and the device parent-child information 142 corresponding to the device identified in step S21. Then, the generation rule prediction unit 115 stores the generated input data DT0 in the information storage area 130, for example. After that, the generation rule prediction unit 115 inputs the input data DT0 stored in the information storage area 130 to the learning model MD, for example. Then, the generation rule prediction unit 115 identifies the first operation plan rule information 132 indicated by the information output from the learning model MD in association with the input of the input data DT0. A specific example of the input data DT0 will be described below.

[0137] [Example of input data DT0] Next, a specific example of the input data DT0 will be described with reference to Fig. 35. The input data DT0 is a diagram for explaining a specific example of the input data DT0.

[0138] The input data DT0 shown in Fig. 35 has, for example, a "parent-child connection vector," a "type vector," a "name vector," and a "number of vehicles" as items, similar to the teacher data DT described in Fig. 27 etc. In other words, the input data DT0 shown in Fig. 35 is data that has, for example, items other than "operation plan rule information" among the items of the teacher data DT described in Fig. 27 etc.

[0139] Specifically, in the input data DT0 shown in FIG. 35, for example, the "parent-child connection vector" is set to "0,-1,0", the "type vector" is set to "Ki", ​​the "name vector" is set to "Ni", and the "number of units" is set to "1".

[0140] [Specific example of the process in step S24] Next, a specific example of the process of step S24 will be described. Fig. 22 and Fig. 23 are diagrams for explaining a specific example of step S24. Specifically, Fig. 22 is a diagram for explaining a specific example of the operation plan rule information 132 (hereinafter also referred to as the conditional operation plan rule information 132) including a portion corresponding to the equipment symbol L1. Also, Fig. 23 is a diagram for explaining another specific example of the conditional operation plan rule information 132 including a portion corresponding to the equipment symbol L1. Note that, unlike the conditional operation plan rule information 132 shown in Fig. 22, the description of the portions other than the equipment symbol L1 is omitted in the conditional operation plan rule information 132 shown in Fig. 23.

[0141] In the examples shown in Fig. 14 and the like, a case where there is one driving plan rule information 132 corresponding to each type has been described. In contrast, in the examples shown in Fig. 22 and Fig. 23, a case where there are multiple driving plan rule information 132 corresponding to each type has been described. That is, in the examples shown in Fig. 22 and Fig. 23, a case where each driving plan rule information 132 exists for each unit that further subdivides the type will be described.

[0142] Specifically, the driving plan rule information 132 (hereinafter also referred to as driving plan rule information 132c) shown in Figures 22 and 23 includes, for example, one or more conditional driving plan rule information 132 in addition to driving plan rule information 132 (hereinafter also referred to as normal driving plan rule information 132) that does not include a portion corresponding to the equipment symbol L1. Then, in step S24 of Figure 8, for example, by using the learning model MD, the learning model MD specifies either the normal driving plan rule information 132 or one or more conditional driving plan rule information 132 as the driving plan rule information 132 corresponding to the equipment specified in step S21.

[0143] More specifically, in step S24 of FIG. 8, if the name of the equipment corresponding to the equipment identified in step S21 (for example, the name of the equipment included in the information set in the "attribute" of the equipment list information 141a) is not a transfer pump, the learning model MD outputs information indicating normal operation plan rule information 132 (operation plan rule information 132 that does not include the part corresponding to the equipment symbol L1) from the operation plan rule information 132 shown in FIG. 22 as information indicating the operation plan rule information 132 corresponding to the equipment identified in step S21.

[0144] Furthermore, in step S24 of FIG. 8, for example, when the name of the equipment corresponding to the equipment identified in step S21 is a transfer pump, the learning model MD outputs information indicating the conditional operation plan rule information 132 (operation plan rule information 132 including a portion corresponding to equipment symbol L1) from the operation plan rule information 132 shown in FIG. 22 as information indicating the operation plan rule information 132 corresponding to the equipment identified in step S21.

[0145] Here, for example, if the name of the equipment corresponding to the equipment identified in step S21 is a transfer pump and the number of transfer pumps (for example, the number included in the information set in the "attributes" of the equipment list information 141a) is multiple, the learning model MD outputs information indicating the conditional operation plan rule information 132 corresponding to the transfer pump and the number of transfer pumps as information indicating the operation plan rule information 132 corresponding to the equipment identified in step S21.

[0146] That is, for example, when the number of transfer pumps is two, the learning model MD outputs information indicating conditional operation plan rule information 132 that includes, in addition to the portion corresponding to equipment symbol L1, a portion corresponding to equipment symbol L11 from the operation plan rule information 132 shown in FIG. 23 (in other words, conditional operation plan rule information 132 that does not include the portion corresponding to equipment symbol L12).

[0147] In addition, when the number of transfer pumps is three, for example, the learning model MD outputs information indicating conditional operation plan rule information 132 that includes, in addition to the portion corresponding to equipment symbol L1, a portion corresponding to equipment symbol L12 (in other words, conditional operation plan rule information 132 that does not include the portion corresponding to equipment symbol L11) from the operation plan rule information 132 shown in FIG. 23.

[0148] Returning to Fig. 8, the driving plan generating unit 116, for example, uses at least one of the connection point information 133, the device list information 141a, the connection list information 141b, and the device parent-child information 142 as input, converts the variables included in the driving plan rule information 132 identified in step S24 by executing an expansion program (not shown), and generates driving plan information 151 corresponding to the device identified in step S21 from the driving plan rule information 132 identified in step S24 (step S25 in Fig. 8). Then, the information management unit 112, for example, stores the driving plan information 151 generated by the driving plan generating unit 116 in the information storage area 130. A specific example of the driving plan information 151 will be described below.

[0149] [Example of operation plan information 151] Fig. 24 and Fig. 25 are diagrams for explaining a specific example of the driving plan information 151. Specifically, Fig. 24 is a diagram for explaining a specific example of the driving plan information 151 (hereinafter also referred to as driving plan information 151a) generated from the driving plan rule information 132a explained in Fig. 14. Also, Fig. 25 is a diagram for explaining a specific example of the driving plan information 151 (hereinafter also referred to as driving plan information 151b) generated from the driving plan rule information 132b explained in Fig. 15.

[0150] Specifically, for example, when generating operation plan information 151a for transfer pump OB2 in equipment information 141 described in Fig. 17, the information identification unit 114 refers to type parent-child information 131a described in Fig. 9, for example, and identifies "pump" that is the parent of "volute pump" corresponding to the type of transfer pump OB2 as the "type" of transfer pump OB2. Then, the information identification unit 114 refers to device type information 131b1 described in Fig. 10, for example, and identifies operation plan rule information 132a (operation plan rule information 132a described in Fig. 14) corresponding to "132a" set in "operation plan rule information" in information (information in the first row) in which "type" is set to "pump."

[0151] Next, in the device type information 131b1 described in Fig. 10, in the information in which "type" is set to "pump", "connection point information" is set to "first connection point: upstream" and "second connection point: downstream". And, the facility information 141 described in Fig. 17 indicates, for example, that the sludge storage tank OB1 and the transfer pump OB2 are connected, and that the transfer pump OB2 and the sludge hopper OB3 are connected.

[0152] Therefore, for example, when the left connection point of the transfer pump OB2 shown in Fig. 17 is the first connection point, the operation plan generating unit 116 determines that the sludge storage tank OB1 connected at the left connection point of the transfer pump OB2 is an upstream device of the transfer pump OB2. Also, for example, when the right connection point of the transfer pump OB2 shown in Fig. 17 is the second connection point, the operation plan generating unit 116 determines that the sludge hopper OB3 connected at the right connection point of the transfer pump OB2 is a downstream device of the transfer pump OB2.

[0153] Therefore, in this case, the operation plan generator 116 executes the expansion program included in the operation plan rule information 132a shown in Fig. 14, thereby interpreting, for example, "%Upstream.Ls%" in the operation plan rule information 132a shown in Fig. 14 as "a level gauge installed in the upstream sludge storage tank" and setting a "sludge storage tank level gauge", and interpreting "%Downstream.Ls%" in the operation plan rule information 132a shown in Fig. 14 as "a level gauge installed in the downstream sludge hopper" and setting a "sludge hopper level gauge", as shown in Fig. 24. Explanation of other information included in Fig. 24 will be omitted.

[0154] Also, for example, when generating operation plan information 151b for the sludge storage tank level gauge OB11 in the equipment information 141 described in Fig. 17, the information identification unit 114 refers to, for example, the type parent-child information 131a described in Fig. 9, and identifies "level gauge" which is the parent of "level gauge (electrode rod type)" corresponding to the type of the sludge storage tank level gauge OB11. Then, the information identification unit 114 refers to, for example, the device type information 131b1 described in Fig. 10, and identifies operation plan rule information 132b (operation plan rule information 132b described in Fig. 15) corresponding to "132b" set in "operation plan rule information" in the information in which "type" is set to "level gauge".

[0155] Next, the equipment parent-child information 142 described in Fig. 20 indicates that the parent of the sludge storage tank level gauge OB11 is the sludge storage tank OB1. Therefore, in this case, the operation plan generator 116 executes the expansion program included in the operation plan rule information 132b shown in Fig. 15, and sets, for example, "sludge storage tank" to "%Parent.Name%" in the operation plan rule information 132b shown in Fig. 15, as shown in Fig. 25. Descriptions of other information included in Fig. 25 will be omitted.

[0156] Returning to FIG. 8, the information identifying unit 114 determines, for example, whether or not all devices included in the facility information 141 have been identified in step S21 (step S26 in FIG. 8).

[0157] As a result, when it is determined that all devices have not been identified (NO in step S26), the information identifying unit 114 performs, for example, step S21 and subsequent steps again.

[0158] On the other hand, if it is determined that all the devices have been identified (YES in step S26), the operation plan output unit 117 outputs each of the operation plan information 151 generated in step S25 (step S27 in FIG. 8).

[0159] Specifically, the driving plan output unit 117 outputs, for example, each of the driving plan information 151 generated in step S25 to the operation terminal 5.

[0160] In addition, for example, after step S27, the operator may input a judgment result of whether or not the driving plan information 151 generated in step S25 (i.e., the driving plan information 151 generated from the driving plan rule information 132 specified by the learning model MD) is appropriate driving plan information 151 to the control device 1. In this case, the model learning unit 118 may generate other teacher data (not shown) based on the judgment result by the operator on whether or not the driving plan information 151 generated in step S25 is appropriate, and may further train the learning model MD using the generated other teacher data. Specifically, in this case, the model learning unit 118 may generate other teacher data including, for example, the input data DT0 input to the learning model MD in step S24 and the first driving plan rule information 132 indicated by the information output from the learning model MD in step S24, and may further train the learning model MD using the generated other teacher data.

[0161] This enables the control device 1 to, for example, further improve the determination accuracy using the learning model MD.

[0162] [Example of output screen OP] Next, a specific example of the output screen OP for the driving plan information 151 in the operation terminal 5 will be described. Fig. 26 is a diagram for explaining a specific example of the output screen OP for the driving plan information 151 in the operation terminal 5.

[0163] 26, the driving plan output unit 117 may output, for example, the device parent-child information 142 in addition to the driving plan information 151. Also, the driving plan output unit 117 may have a function that enables editing of the device parent-child information 142.

[0164] Specifically, in this case, the operation plan output unit 117 may, for example, output the equipment parent-child information 142 to the output screen OP, and then accept designation (designation by an operator) of an equipment included in the equipment parent-child information 142. And, the operation plan output unit 117 may, for example, output the operation plan information 151 corresponding to the equipment for which the designation has been accepted, from among the generated operation plan information 151 (the operation plan information 151 stored in the information storage area 130).

[0165] This allows an operator viewing the output screen OP to view, for example, the device parent-child information 142 as well, thereby making it possible to further improve the readability of the operation plan information 151.

[0166] 26, the operation plan output unit 117 may also output, on the output screen OP, part information IM indicating a list of parts that can be added to the operation plan information 151. Specifically, in the example shown in Fig. 26, part information IM including, as parts, "single operation" indicating the addition of an isolated operation circuit, "number control" indicating the addition of a device number control circuit, etc. is displayed.

[0167] As a result, if an operator viewing the output screen OP determines that there is a deficiency in the content of the operation plan information 151, the operator can easily add content corresponding to the specified part to the operation plan information 151 by specifying a part included in the part information IM.

[0168] In addition, the driving plan output unit 117 may have a function that enables editing of not only the driving plan information 151 but also the driving plan rule information 132, for example.

[0169] The facility information generating unit 113 may, for example, reflect information indicating the operation plan information 151 generated in step S25 in the facility information 141 stored in the information storage area 130.

[0170] In this way, the control device 1 in this embodiment stores in the storage unit, for example, device standard information 131 in which operation plan rule information 132 corresponding to each type and connection point information 133 indicating attributes of connection points between the device corresponding to each type and other devices are associated with each other for each type of device. Then, the control device 1 accepts input of facility information 141 including, for example, device list information 141a indicating one or more devices for which operation plan information 151 is generated, connection list information 141b indicating connection relationships between the one or more devices, and device parent-child information 142 indicating parent-child relationships among the one or more devices. Next, the control device 1 refers to the device standard information 131 stored in the information storage area 130, for example, and specifies the first device standard information 131 corresponding to the first type for each device for each one or more devices.

[0171] Thereafter, the control device 1 inputs, for each of one or more devices, information generated using at least one of the connection point information 133 corresponding to the type of the learning device, the device list information 141a corresponding to the learning device, the connection list information 141b corresponding to the learning device, and the device parent-child information 142 corresponding to the learning device, into the learning model MD that has been subjected to machine learning of the teacher data DT including information generated using at least one of the connection point information 133 corresponding to the type of the learning device, the device list information 141a corresponding to the learning device, the connection list information 141b corresponding to the learning device, and the device parent-child information 142 corresponding to the learning device, thereby specifying the first driving plan rule information 132 corresponding to each of the one or more devices. Then, the control device 1 generates, for example, driving plan information 151 corresponding to one or more devices based on each of the specified first driving plan rule information 132.

[0172] Furthermore, the control device 1 in this embodiment generates a learning model MD by performing machine learning on the teacher data DT, for example, before the process of accepting the input of the facility information 141.

[0173] As a result, the control device 1 in this embodiment can automatically and easily generate the operation plan information 151 corresponding to one or more devices for which the operation plan information 151 is to be generated, for example, by using the learning model MD. Therefore, the control device 1 can reduce the workload of an operator involved in generating the operation plan information 151, for example.

[0174] In addition, the control device 1 in this embodiment can automatically generate the operation plan information 151, for example, thereby making it possible to prevent human errors such as failure to create or update the operation plan information 151 compared to the case where an operator manually generates the operation plan information 151.

[0175] Furthermore, the devices whose information is included in the device list information 141a and the connection list information 141b respectively match the devices whose information is included in the parent-child information 142. Therefore, the control device 1 in this embodiment can prevent, for example, omissions in the creation of the device list information 141a, the connection list information 141b, and the parent-child information 142.

[0176] In addition, the control device 1 in this embodiment can also consolidate the operation plan information 151 for each device by generating, for example, device parent-child information 142 for one or more devices. Therefore, the control device 1 can facilitate reuse of the operation plan information 151 corresponding to each device having a parent-child relationship.

[0177] In addition, the control device 1 in this embodiment generates operation plan information 151 using, for example, the names of equipment included in the facility information 141, thereby making it possible to prevent variation in the names of equipment included in the operation plan information 151.

[0178] In addition, the control device 1 in this embodiment generates operation plan information 151 using, for example, the names of equipment included in the facility information 141, making it possible to easily generate new operation plan information 151 by reusing operation plan information 151 generated in the past.

[0179] In addition, in the present embodiment, the control device 1 is capable of detecting a lack of information in the connection point information 133 or the equipment information 141, for example, when it is unable to generate (execute a deployment program) the operation plan information 151 from the operation plan rule information 132 corresponding to each device.

[0180] Furthermore, the control device 1 in this embodiment can further improve the judgment accuracy of the learning model MD by, for example, further learning about the first driving plan rule information 132 that the worker judges to be appropriate from the first driving plan rule information 132 identified by the learning model MD (for example, new driving plan rule information 132 that the worker was not aware of).

[0181] [Operation plan generation system 1000 according to the second embodiment] Next, the configuration of the driving plan generating system 1000 in the second embodiment will be described. Below, differences from the driving plan generating system 1000 in the first embodiment will be described.

[0182] [Function of control device 1] First, the function of the control device 1 in the second embodiment will be described. Fig. 30 is a block diagram of the function of the control device 1 in the second embodiment. Fig. 31 is a block diagram of information stored in the information storage area 130 in the second embodiment.

[0183] As shown in FIG. 30, the control device 1 realizes various functions including an information receiving unit 111, an information management unit 112, an equipment information generation unit 113, an information identification unit 114, a generation rule prediction unit 115, an operation plan generation unit 116, an operation plan output unit 117, a model learning unit 118, and a generation rule identification unit 119, by organic cooperation between hardware such as a CPU 101 and a memory 102 and programs.

[0184] 31, the control device 1 stores, for example, equipment standard information 131, operation plan rule information 132, connection point information 133, facility information 141, equipment parent-child information 142, operation plan information 151, operation plan information 152, and learning model MD in the information storage area 130. Specifically, the equipment standard information 131 includes, for example, type parent-child information 131a and type detailed information 131b. Furthermore, the facility information 141 includes, for example, equipment list information 141a and connection list information 141b.

[0185] The following describes the main process of generating an operation plan in the second embodiment. Note that the information preparation process, model generation process, and facility information generation process in the second embodiment are the same as those in the first embodiment, so the description will be omitted.

[0186] In the main process of generating a driving plan in the second embodiment, for example, the driving plan rule information 132 is specified by a plurality of processes. In the main process of generating a driving plan in the second embodiment, for example, the driving plan information 151 and the driving plan information 152 are generated by using each of the driving plan rule information 132 specified by the plurality of processes.

[0187] First, a process of identifying the driving plan rule information 132 using the learning model MD (hereinafter, also referred to as a first generation rule identifying process) in the main process of generating a driving plan in the second embodiment will be described.

[0188] As in the first embodiment, the generation rule prediction unit 115, for example, by using the learning model MD stored in the information storage area 130, identifies, for each of one or more pieces of equipment included in the facility information 141, the first operation plan rule information 132 corresponding to each piece of equipment from the operation plan rule information 132 included in the equipment standard information 131 stored in the information storage area 130.

[0189] Next, a process of identifying the driving plan generation rule information 132 without using the learning model MD (hereinafter, also referred to as a second generation rule identification process) in the main driving plan generation process in the second embodiment will be described.

[0190] The information identification unit 114, for example, refers to the equipment standard information 131 stored in the information storage area 130, and identifies, for each of one or more pieces of equipment included in the facility information 141, the equipment standard information 131 (first equipment standard information 131) corresponding to the type (first type) in which each piece of equipment is included.

[0191] Specifically, the information identification unit 114, for example, refers to type parent-child information 131a included in the equipment standard information 131 stored in the information storage area 130, and identifies the type of each equipment for each of one or more equipment included in the equipment information 141.

[0192] The generation rule identification unit 119, for example, for each of one or more pieces of equipment included in the equipment information 141, identifies the operation plan rule information 132 included in the first equipment standard information 131 corresponding to each piece of equipment as the operation plan rule information 132 corresponding to each piece of equipment (hereinafter also referred to as the second operation plan rule information 132).

[0193] This allows the control device 1 in this embodiment to specify the second operation plan rule information 132 without using, for example, the learning model MD. Therefore, even if the determination accuracy of the first operation plan rule information 132 specified using, for example, the learning model MD is not sufficient, the control device 1 can specify the appropriate second operation plan rule information 132 corresponding to each device.

[0194] In addition, the control device 1 in this embodiment does not necessarily need to improve the judgment accuracy of the learning model MD as much as possible by outputting, for example, the second operation plan rule information 132 identified without using the learning model MD. Therefore, the control device 1 can suppress the occurrence of overlearning in the learning model MD.

[0195] The connection point information 133, the equipment list information 141a, the connection list information 141b, and the equipment parent-child information 142 corresponding to each operation plan rule information 132 may be converted into data (hereinafter also referred to as vector data) in the same format as the input data DT0 described in Fig. 35 and stored in the information storage area 130. The generation rule identification unit 119 may convert the connection point information 133, the equipment list information 141a, the connection list information 141b, and the equipment parent-child information 142 corresponding to each equipment included in the facility information 141 into vector data, and further identify the second operation plan rule information 132 corresponding to each equipment by matching the converted vector data with vector data (vector data corresponding to each operation plan rule information 132) stored in the information storage area 130.

[0196] Next, a process of generating and outputting the driving plan information 151 and the driving plan information 152 (hereinafter, also referred to as a driving plan output process) among the main process of generating a driving plan in the second embodiment will be described.

[0197] The operation plan generation unit 116 generates operation plan information 151 corresponding to one or more pieces of equipment included in the equipment information 141, for example, based on the first operation plan rule information 132 identified by the generation rule prediction unit 115 (the first operation plan rule information 132 corresponding to each of the one or more pieces of equipment included in the equipment information 141).

[0198] Specifically, the operation plan generating unit 116, for example, refers to the connection point information 133 corresponding to the equipment standard information 131 stored in the information storage area 130, and for each of one or more equipment included in the equipment information 141 stored in the information storage area 130, identifies a connection point corresponding to a variable in the first operation plan rule information 132 corresponding to each equipment. Then, for example, for each of one or more equipment included in the equipment information 141, the operation plan generating unit 116 identifies an equipment connected at a connection point corresponding to each equipment as a first equipment corresponding to a variable in the first operation plan rule information 132 corresponding to each equipment. After that, the operation plan generating unit 116 generates operation plan information 151 corresponding to one or more equipment included in the equipment information 141 by setting the value of the variable in the first operation plan rule information 132 corresponding to each equipment to a value indicating the first equipment corresponding to the variable in the first operation plan rule information 132 corresponding to each equipment, for example, for one or more equipment included in the equipment information 141.

[0199] Similarly, the operation plan generation unit 116 generates operation plan information 152 corresponding to one or more pieces of equipment included in the equipment information 141, for example, based on the second operation plan rule information 132 identified by the generation rule identification unit 119 (the second operation plan rule information 132 corresponding to each of the one or more pieces of equipment included in the equipment information 141).

[0200] The driving plan output unit 117 outputs, for example, at least one of the driving plan information 151 and the driving plan information 152 generated by the driving plan generating unit 116. Specifically, the driving plan output unit 117 outputs, for example, the driving plan information 151 and the driving plan information 152 to the operation terminal 5.

[0201] [Flowchart of the main process for generating driving plans] Next, a description will be given of a flow chart of the main process of generating an operation plan in the second embodiment. Fig. 32 is a flow chart for explaining the main process of generating an operation plan in the second embodiment.

[0202] The information identifying unit 114, for example, identifies one device included in the facility information 141 stored in the information storage area 130 (step S41 in FIG. 32). Specifically, the information identifying unit 114, for example, identifies one device included in the facility information 141 generated in the facility information generation process.

[0203] Then, the information identifying unit 114, for example, refers to type parent-child information 131a included in the device standard information 131 stored in the information storage area 130, and identifies the type to which the device identified in step S41 belongs (step S42 in FIG. 32).

[0204] Next, the information identifying unit 114, for example, refers to the device standard information 131 stored in the information storage area 130, and identifies the first device standard information 131 corresponding to the type identified in step S42 (step S43 in FIG. 32).

[0205] Thereafter, the generation rule prediction unit 115, for example, by using the learning model MD stored in the information storage area 130, identifies the first driving plan rule information 132 corresponding to the equipment identified in step S41 from the driving plan rule information 132 stored in the information storage area 130 (step S44 in FIG. 8).

[0206] Specifically, as shown in FIG. 21, the generation rule prediction unit 115 generates input data DT0 from at least one of the connection point information 133 corresponding to the first device standard information 131 identified in step S43, the device list information 141a corresponding to the device identified in step S41, the connection list information 141b corresponding to the device identified in step S41, and the device parent-child information 142 corresponding to the device identified in step S41. Then, the generation rule prediction unit 115 stores the generated input data DT0 in the information storage area 130, for example. After that, the generation rule prediction unit 115 inputs the input data DT0 stored in the information storage area 130 to the learning model MD, for example. Then, the generation rule prediction unit 115 identifies the first operation plan rule information 132 indicated by the information output from the learning model MD in association with the input of the input data DT0, for example.

[0207] In addition, the generation rule identification unit 119, for example, identifies the second driving plan rule information 132 corresponding to the equipment identified in step S41 from the driving plan rule information 132 stored in the information storage area 130 without using the learning model MD stored in the information storage area 130 (step S45 in Figure 32).

[0208] Specifically, the generation rule identification unit 119 identifies, for example, the operation plan rule information 132 included in the first equipment standard information 131 corresponding to the equipment identified in step S41 as the second operation plan rule information 132 corresponding to the equipment identified in step S41. A specific example of the process of step S45 will be described below.

[0209] [Specific example of the process in step S45] Fig. 33 and Fig. 34 are diagrams for explaining a specific example of step S45. Specifically, Fig. 33 is a diagram for explaining a specific example of the conditional driving plan rule information 132 including a portion corresponding to the equipment symbol L1a. Also, Fig. 34 is a diagram for explaining another specific example of the conditional driving plan rule information 132 including a portion corresponding to the equipment symbol L1a. Note that, unlike the conditional driving plan rule information 132 shown in Fig. 33, the conditional driving plan rule information 132 shown in Fig. 34 omits notation of portions other than the equipment symbol L1.

[0210] Specifically, the driving plan rule information 132 (hereinafter also referred to as driving plan rule information 132d) shown in Figures 33 and 34 includes, for example, normal driving plan rule information 132 that does not include a portion corresponding to the equipment symbol L1a, as well as one or more conditional driving plan rule information 132. Then, in step S45 of Figure 32, the generation rule identification unit 119 identifies, for example, one of the normal driving plan rule information 132 and the one or more conditional driving plan rule information 132 as the driving plan rule information 132 corresponding to the equipment identified in step S41, without using the learning model MD.

[0211] More specifically, in step S45 of FIG. 32, if the name of the equipment corresponding to the equipment identified in step S41 (for example, the name of the equipment included in the information set in the “attributes” of the equipment list information 141a) is not a transfer pump, the generation rule identification unit 119 identifies normal operation plan rule information 132 as the operation plan rule information 132 corresponding to the equipment identified in step S41.

[0212] That is, in this case, the generation rule identification unit 119 determines that the condition, for example, "Me.Name="Transfer Pump" is not satisfied, and identifies normal operation plan rule information 132 (operation plan rule information 132 that does not include the part corresponding to the equipment symbol L1a) from the operation plan rule information 132 shown in FIG. 33.

[0213] On the other hand, in step S45 of Figure 32, for example, if the name of the equipment corresponding to the equipment identified in step S41 is a transfer pump, the generation rule identification unit 119 identifies conditional operation plan rule information 132 as the operation plan rule information 132 corresponding to the equipment identified in step S41.

[0214] That is, in this case, the generation rule identification unit 119 determines that the condition, for example, "Me.Name="Transfer Pump" is satisfied, and identifies the conditional operation plan rule information 132 (operation plan rule information 132 including a part corresponding to the equipment symbol L1a) from the operation plan rule information 132 shown in FIG. 33.

[0215] Here, in step S45 of Figure 32, for example, if the name of the equipment corresponding to the equipment identified in step S41 is a transfer pump and the number of transfer pumps (for example, the number included in the information set in the ``attributes'' of the equipment list information 141a) is multiple, the generation rule identification unit 119 identifies the conditional operation plan rule information 132 corresponding to the transfer pump and the number of transfer pumps as the operation plan rule information 132 corresponding to the equipment identified in step S41.

[0216] In other words, for example, when the number of transfer pumps is two, the generation rule identification unit 119 determines that the condition "Me.Number="2"" is further satisfied, and identifies conditional operation plan rule information 132 shown in FIG. 34 that includes a portion corresponding to equipment symbol L1a in addition to the portion corresponding to equipment symbol L11a (in other words, conditional operation plan rule information 132 that does not include the portion corresponding to equipment symbol L12a).

[0217] Furthermore, for example, if the number of transfer pumps is three, the generation rule identification unit 119 determines that the condition "Me.Number="3"" is further satisfied, and identifies conditional operation plan rule information 132 shown in FIG. 34 that includes a portion corresponding to equipment symbol L1a as well as a portion corresponding to equipment symbol L12a (in other words, conditional operation plan rule information 132 that does not include a portion corresponding to equipment symbol L11a).

[0218] Returning to Fig. 32, the operation plan generating unit 116 generates operation plan information 151 corresponding to the equipment identified in step S41 from the operation plan rule information 132 identified in step S44 by converting variables included in the operation plan rule information 132 identified in step S44 by executing an expansion program using at least one of the connection point information 133, the equipment list information 141a, the connection list information 141b, and the equipment parent-child information 142 as input. Also, the operation plan generating unit 116 generates operation plan information 152 corresponding to the equipment identified in step S41 from the operation plan rule information 132 identified in step S45 by converting variables included in the operation plan rule information 132 identified in step S45 by executing an expansion program (step S46 in Fig. 32). After that, the information management unit 112 stores, for example, the driving plan information 151 and the driving plan information 152 generated by the driving plan generation unit 116 in the information storage area 130 .

[0219] Then, the information identifying unit 114 determines, for example, whether or not all devices included in the facility information 141 have been identified in step S41 (step S47 in FIG. 32).

[0220] As a result, when it is determined that all devices have not been identified (NO in step S47), the information identifying unit 114 performs, for example, step S41 and subsequent steps again.

[0221] On the other hand, when it is determined that all devices have been identified (YES in step S47), the operation plan output unit 117 outputs each of the operation plan information 151 and the operation plan information 152 generated in step S46 (step S48 in FIG. 32).

[0222] Specifically, the driving plan output unit 117 outputs, for example, the driving plan information 151 and the driving plan information 152 generated in step S46 to the operation terminal 5.

[0223] In this way, the control device 1 in this embodiment, for example, refers to the equipment standard information 131 stored in the information storage area 130, and for one or more equipment included in the facility information 141 stored in the information storage area 130, specifies the first equipment standard information 131 corresponding to the first type for each equipment, and for one or more equipment included in the facility information 141, specifies the second operation plan rule information 132 included in the first equipment standard information 131 corresponding to each equipment. Then, for example, the control device 1 refers to the connection point information 133 included in the equipment standard information 131 corresponding to each equipment for one or more equipment included in the facility information 141, and specifies the connection point corresponding to the variable in the second operation plan rule information 132 corresponding to each equipment. Furthermore, the control device 1, for example, refers to the equipment information 141 stored in the information storage area 130, and for one or more equipment included in the facility information 141, specifies the equipment connected at the connection point corresponding to each equipment as the first equipment corresponding to the variable in the second operation plan rule information 132 corresponding to each equipment. Then, the control device 1 generates operation plan information 152 corresponding to one or more pieces of equipment, for example, by determining, for each piece of equipment included in the equipment information 141, the value of the variable in the second operation plan rule information 132 corresponding to each piece of equipment as a value indicating the first equipment corresponding to the variable in the second operation plan rule information 132 corresponding to each piece of equipment.

[0224] Furthermore, the control device 1 in this embodiment outputs, for example, for each of one or more devices included in the facility information 141, operation plan information 151 and operation plan information 152 corresponding to each device.

[0225] That is, the control device 1 in this embodiment, for example, performs a plurality of processes (a first generation rule identification process and a second generation rule identification process) to identify the operation plan rule information 132 corresponding to each device. Then, the control device 1 generates and outputs the operation plan information 151 and the operation plan information 152 corresponding to each device from each of the operation plan rule information 132 identified by the plurality of processes.

[0226] Thereby, the control device 1 in the present embodiment can allow the worker to refer to, for example, the operation plan information 151 and the operation plan information 152 corresponding to each device. Therefore, the worker can adopt, for example, the more appropriate one of the operation plan information 151 and the operation plan information 152 corresponding to each device.

[0227] In addition, the control device 1 in this embodiment can further improve the judgment accuracy of the learning model MD by, for example, conducting further learning on the operation plan information 151 and the operation plan information 152 corresponding to each device that the operator judges to be necessary. [Explanation of symbols]

[0228] 1: Control device 5: Operation terminal 101: CPU 102: Memory 103: Communication device 104: Storage medium 105: Bus 111: Information receiving unit 112: Information management department 113: Equipment information generation department 114: Information identification section 115: Driving plan generation section 116: Operation plan output unit 130: Information storage area 131: Equipment standard information 131a: Type parent-child information 131b: Type detailed information 132: Operation plan rule information 132a: driving plan rule information 132b: driving plan rule information 132c: Operation plan rule information 133: Connection point information 141: Facility information 141a: Equipment list information 141b: Connection list information 142: Device parent-child information 151: Driving plan information 151a: Driving plan information 151b: Operation plan information 152: Operation plan information 1000: Driving plan generation system DT: Training data L1: Footprint L1a: Footprint L11: Footprint L11a: Footprint L12: Footprint L12a: Footprint MD: Learning model NW: Network OB1: Sludge storage tank OB11: Sludge storage tank level gauge OB2: Transfer pump OB3: Sludge hopper OB31: Sludge hopper level gauge S: Symbol

Claims

1. storing, for each of a plurality of types of equipment, equipment standard information including a generation rule for an operation plan corresponding to each type and connection point information indicating attributes of connection points between the equipment corresponding to each type and other equipment in a storage unit; Accepting input of facility information including device information indicating one or more devices, connection information indicating a connection relationship between the one or more devices, and parent-child information indicating a parent-child relationship between the one or more devices; A learning model is obtained by machine learning training data including information generated using at least one of the connection point information corresponding to a type of a learning device, the device information corresponding to the learning device, the connection information corresponding to the learning device, and the parent-child information corresponding to the learning device, and information indicating the generation rule corresponding to the learning device. For each of the one or more devices, information generated using at least one of the connection point information corresponding to the type of each device, the device information corresponding to each device, the connection information corresponding to each device, and the parent-child information corresponding to each device is input to the learning model, thereby identifying a first generation rule corresponding to each device, for each of the one or more devices; generating a first operation plan corresponding to the one or more devices based on each of the identified first generation rules; A driving plan generating method characterized in that the processing is executed by a computer.

2. Furthermore, before the process of accepting the input of the facility information, the learning model is generated by performing machine learning on the teacher data.

2. The method for generating a driving plan according to claim 1, wherein the processing is executed by a computer.

3. Further, for each of the first or more devices, other teacher data is generated, the teacher data including information generated using at least one of the connection point information corresponding to the type of each device, the device information corresponding to each device, the connection information corresponding to each device, and the parent-child information corresponding to each device, and the first generation rule corresponding to each device; Further performing machine learning of the learning model by using the other teacher data corresponding to each of the one or more devices.

2. The method for generating a driving plan according to claim 1, wherein the processing is executed by a computer.

4. Further, by referring to the device standard information, for each of the one or more devices, first device standard information corresponding to each device type is specified; identifying a second generation rule included in the first device standard information corresponding to each of the one or more devices; for each of the one or more devices, referring to the connection point information included in the first device standard information corresponding to each device, identify a connection point corresponding to a variable in the second generation rule corresponding to each device; With reference to the facility information, for each of the one or more devices, a device connected at the connection point corresponding to each device is identified as a first device corresponding to the variable in the second generation rule corresponding to each device; generating a second operation plan corresponding to the one or more appliances by setting a value of the variable in the second generation rule corresponding to each appliance to a value indicating the first appliance corresponding to the variable in the second generation rule corresponding to each appliance; outputting the first operation plan and the second operation plan corresponding to each of the one or more devices; 4. The method for generating a driving plan according to claim 3, wherein the processing is executed by a computer.

5. storing, for each of a plurality of types of equipment, equipment standard information including a generation rule for an operation plan corresponding to each type and connection point information indicating attributes of connection points between the equipment corresponding to each type and other equipment in a storage unit; Accepting input of facility information including device information indicating one or more devices, connection information indicating a connection relationship between the one or more devices, and parent-child information indicating a parent-child relationship between the one or more devices; A learning model is obtained by machine learning training data including information generated using at least one of the connection point information corresponding to a type of a learning device, the device information corresponding to the learning device, the connection information corresponding to the learning device, and the parent-child information corresponding to the learning device, and information indicating the generation rule corresponding to the learning device. For each of the one or more devices, information generated using at least one of the connection point information corresponding to the type of each device, the device information corresponding to each device, the connection information corresponding to each device, and the parent-child information corresponding to each device is input to the learning model, thereby identifying a first generation rule corresponding to each device, for each of the one or more devices; generating a first operation plan corresponding to the one or more devices based on each of the identified first generation rules; A driving plan generating program that causes a computer to execute a process.

6. an information management unit that stores in a storage unit, for each type of a plurality of devices, device standard information including a generation rule for an operation plan corresponding to each type and connection point information indicating attributes of connection points between the device corresponding to each type and other devices; an information receiving unit that receives input of facility information including device information indicating one or more devices, connection information indicating a connection relationship between the one or more devices, and parent-child information indicating a parent-child relationship between the one or more devices; a generation rule prediction unit that identifies a first generation rule corresponding to each device for each of the one or more devices by inputting, for each of the one or more devices, information generated using at least one of the connection point information corresponding to the type of learning device, the device information corresponding to the learning device, the connection information corresponding to the learning device, and the parent-child information corresponding to the learning device, into a learning model that has been subjected to machine learning of teacher data including information generated using at least one of the connection point information corresponding to the type of learning device, the device information corresponding to the learning device, the connection information corresponding to the learning device, and the parent-child information corresponding to the learning device, and information indicating the generation rule corresponding to the learning device; and an operation plan generating unit that generates a first operation plan corresponding to the one or more devices based on each of the identified first generation rules. A driving plan generating device characterized by:

Images