Design support apparatus and design support system

Abstract

To provide a design support device and a design support system for improving the efficiency of plant design.SOLUTION: An obtaining unit configured to obtain the graph structure dataset from the storage unit in response to an obtaining request from a terminal that performs each of a plurality of designing processes, an outputting unit configured to output the graph structure dataset to the terminal, and an updating unit configured to update the graph structure dataset stored in the storage unit based on output data of a designing process performed using the graph structure dataset in the terminal. The graph structure data is shared among a plurality of design processes and is detailed from an upstream process to a downstream process of the plant design.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to a design support device and a design support system. [Background technology]

[0002] Design support systems that support plant design to improve the efficiency of plant design are known. For example, Patent Document 1 describes a support system that compares connection information extracted from a 3D model without attributes with connection information extracted from a piping and instrumentation diagram, thereby adding attribute information of the piping and instrumentation diagram to the 3D model and creating a 3D model with attributes. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-5199 Summary of the Invention [Problem to be solved by the invention]

[0004] In the support system described in Patent Document 1, although the assignment of attribute information is automated, drawings are created separately for the piping and instrumentation diagram creation process and the 3D model creation process. As such, in conventional plant design, data is prepared separately for each design process to create drawings, which is one factor that reduces efficiency. In this technical field, there is a demand for improving the efficiency of plant design.

[0005] The present disclosure describes a design support device and a design support system that can improve the efficiency of plant design. [Means for solving the problem]

[0006] (Clause 1) A design support device according to one aspect of the present disclosure is a device for supporting plant design including multiple design processes. The design support device includes: a storage unit that stores graph structure data in which components to be provided in a plant to be designed are defined as nodes and a connection relationship between two components is defined as an edge; an acquisition unit that acquires the graph structure data from the storage unit in response to an acquisition request from a terminal device that performs each of the multiple design processes; an output unit that outputs the graph structure data to the terminal device; and an update unit that updates the graph structure data stored in the storage unit based on output data of a design process performed in the terminal device using the graph structure data. The graph structure data is shared among the multiple design processes and is detailed from an upstream process to a downstream process of the plant design.

[0007] In the design support device, graph structure data is stored in a storage unit, in which components to be installed in a plant to be designed are defined as nodes and a connection relationship between two components is defined as an edge. In response to an acquisition request from a terminal device, the graph structure data is acquired from the storage unit and output to the terminal device. The graph structure data stored in the storage unit is updated based on output data from a design process performed in the terminal device using the graph structure data. A plant can be represented by multiple components for performing a series of processes from raw materials to a final product and the connection relationship between two components. In plant design, the granularity of processes becomes smaller as the design progresses. Although the number of components increases accordingly, the plant can be represented by multiple components and the connection relationship between two components throughout the plant design. Therefore, by defining components to be installed in a plant as nodes and the connection relationship between two components as edges, graph structure data can be shared among multiple design processes without the need to prepare data individually for each design process. This allows the graph structure data to be gradually refined from upstream processes to downstream processes in plant design. As a result, the efficiency of plant design can be improved.

[0008] (Clause 2) In the design support device according to Clause 1, the update unit may add attribute data of the nodes included in the graph structure data to the graph structure data stored in the storage unit.

[0009] In plant design, attributes such as node placement positions are determined in several design processes. The above update process allows the output data of such design processes to be reflected in the graph structure data.

[0010] (Clause 3) In the design support device according to clause 1 or clause 2, the update unit may add attribute data of an edge included in the graph structure data to the graph structure data stored in the storage unit.

[0011] In plant design, attributes such as pipe diameter of edges are determined in several design steps. The above update process allows the output data of such design steps to be reflected in the graph structure data.

[0012] (Clause 4) In the design support device according to any one of clauses 1 to 3, the update unit may add an edge to the graph structure data stored in the storage unit.

[0013] In a plant, common fluids such as heat transfer media, refrigerants, and fuel gases are used to refine raw material fluids, and piping is used to carry these common fluids. In this way, piping may be added in some design processes. The above-described update process allows the output data of such design processes to be reflected in the graph structure data.

[0014] (Clause 5) In the design support device described in any one of Clauses 1 to 4, the update unit may add a node to the graph structure data stored in the storage unit, and add an edge connecting the added node to another node.

[0015] As described above, in plant design, the granularity of the process becomes smaller as the design progresses. Accordingly, components are added, and piping connected to the added components is added. The above-described update process allows the output data of such design processes to be reflected in the graph structure data.

[0016] (Clause 6) A design support system according to another aspect of the present disclosure includes the design support device according to any one of clauses 1 to 5 and a plurality of terminal devices. Each of the plurality of terminal devices performs one of a plurality of design processes.

[0017] Since this design support system includes the above-mentioned design support device, it is possible to improve the efficiency of plant design in the design support system as well.

[0018] (Clause 7) In the design support system described in Clause 6, the plurality of terminal devices may include a first terminal device that performs three-dimensional modeling of the plurality of design processes. The first terminal device may use the graph structure data to display a three-dimensional model of the plant on a display device.

[0019] In this case, the plant to be designed is displayed as a three-dimensional model, and the plant is visualized, allowing the user to easily recognize the layout of each component and each pipe of the plant. [Effects of the Invention]

[0020] According to each aspect and embodiment of the present disclosure, it is possible to improve the efficiency of plant design. [Brief explanation of the drawings]

[0021] [Figure 1] FIG. 1 is a diagram illustrating a schematic configuration of a design support system including a design support apparatus according to an embodiment. [Figure 2] FIG. 2 is a hardware configuration diagram of the design support apparatus shown in FIG. [Figure 3]FIG. 3 is a block diagram showing a functional configuration of the design support apparatus shown in FIG. [Figure 4] FIG. 4 is a diagram illustrating an example of graph structure data. [Figure 5] FIG. 5 is a flowchart showing an example of a design support method performed by the design support apparatus shown in FIG. [Figure 6] FIG. 6 is a diagram illustrating an example of a design process for a plant design. [Figure 7] FIG. 7 is a diagram illustrating an example of graph structure data after the process simulation execution step is performed. [Figure 8] FIG. 8 is a diagram in which the graph structure data shown in FIG. 7 is graphed. [Figure 9] FIG. 9 is a diagram showing an example of a process flow diagram. [Figure 10] FIG. 10 is a diagram showing an example of graph structure data after the process flow diagram preparation step is performed. [Figure 11] FIG. 11 is a diagram in which the graph structure data shown in FIG. 10 is graphed. [Figure 12] FIG. 12 is a diagram showing an example of graph structure data after the plot plan design step has been performed. [Figure 13] FIG. 13 is a diagram showing an example of graph structure data after the hydraulic calculation execution step has been carried out. [Figure 14] FIG. 14 is a diagram illustrating an example of the graph structure data after the piping and instrumentation diagram preparation step is performed. [Figure 15] FIG. 15 is a diagram in which the graph structure data shown in FIG. 14 is graphed. [Figure 16] FIG. 16 is a diagram illustrating an example of a three-dimensional model. [Figure 17] FIG. 17 is a diagram showing an example of graph structure data after the three-dimensional modeling step has been performed. [Figure 18] FIG. 18 is a diagram in which the graph structure data shown in FIG. 17 is graphed. [Figure 19]FIG. 19 is a diagram showing the configuration of a design support program recorded on a recording medium. [Figure 20] FIG. 20 is a diagram showing another example of graph structure data after the three-dimensional modeling step has been performed. [Figure 21] FIG. 21 is a diagram in which the graph structure data shown in FIG. 20 is graphed. DETAILED DESCRIPTION OF THE INVENTION

[0022] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the description of the drawings, the same elements are designated by the same reference numerals, and duplicated description will be omitted.

[0023] First, a design support system including a design support device according to an embodiment will be described with reference to Figures 1 and 2. Figure 1 is a schematic diagram of a design support system including a design support device according to an embodiment. Figure 2 is a hardware configuration diagram of the design support device shown in Figure 1.

[0024] The design support system 1 shown in Figure 1 is a system for supporting plant design. Examples of plants to be designed include oil and gas plants. Examples of oil and gas plants include oil refineries, gas processing plants, natural gas liquefaction plants, petrochemical plants, and chemical manufacturing plants.

[0025] Plant design involves multiple design processes (design phases), such as process simulation, process flow diagram (PFD) preparation, plot plan design, hydraulic calculation, piping and instrument diagram (P&ID) preparation, and 3D modeling. Each design process is described in detail below.

[0026] The design support system 1 includes one or more terminal devices 10 and a design support device 20. Each of the terminal devices 10 and the design support device 20 are communicably connected to each other via a communication network NW. The communication network NW may be configured as either a wired or wireless network. Examples of the communication network NW include the Internet, a mobile communication network, and a WAN (Wide Area Network).

[0027] The terminal device 10 is used by a user (designer) and performs various processes based on the user's operations. Examples of the terminal device 10 include a desktop computer, a laptop computer, a tablet terminal, and a smartphone. The user performs a design process on the terminal device 10, for example, using a dedicated application for each design process. The terminal device 10 performs each of a plurality of design processes. One terminal device 10 may perform only one design process, or may perform two or more design processes.

[0028] The terminal device 10 transmits an acquisition request for acquiring graph structure data, which will be described later, to the design support device 20, and acquires the graph structure data from the design support device 20. The terminal device 10 performs a design process using the graph structure data, and transmits the output data thereof to the design support device 20.

[0029] The design support device 20 is a device that supports plant design. The design support device 20 holds graph structure data that is shared (commonly used) across all design processes. The design support device 20 is configured by an information processing device such as a server device.

[0030] 2, the design support device 20 can be physically configured as a computer including hardware such as a processor 201, a main memory device 202, an auxiliary memory device 203, and a communication device 204. The design support device 20 may be configured from one computer as shown in FIG. 2, or may be configured from multiple computers.

[0031] An example of the processor 201 is a CPU (Central Processing Unit). The main storage device 202 is composed of RAM (Random Access Memory) and ROM (Read Only Memory), etc. Examples of the auxiliary storage device 203 are semiconductor memory and hard disk drives. The auxiliary storage device 203 stores a design support program P (see FIG. 19). The communication device 204 is a device that transmits and receives data to and from other devices via a communication network NW. The communication device 204 is composed of, for example, a network interface card (NIC) or a wireless communication module.

[0032] The processor 201 reads the design support program P stored in the auxiliary storage device 203 into the main storage device 202 and executes it, whereby each piece of hardware operates under the control of the processor 201, and data is read from and written to the main storage device 202 and the auxiliary storage device 203. In this way, each functional unit of the design support device 20 shown in Fig. 3 is realized. Note that each terminal device is also configured by a computer similar to the design support device 20.

[0033] Next, the functional configuration of the design support device 20 will be described with reference to Fig. 3 and Fig. 4. Fig. 3 is a block diagram showing the functional configuration of the design support device shown in Fig. 1. Fig. 4 is a diagram showing an example of graph structure data. As shown in Fig. 3, the design support device 20 includes, as functional elements, an acquisition unit 21, an output unit 22, an update unit 23, and a storage unit 30. The function (operation) of each functional unit will be described in detail in the description of the design support method given below, so here, the function of each functional unit will be briefly described.

[0034] The memory unit 30 is a functional element that stores graph structure data. In this embodiment, the graph structure data is data that defines components provided in a plant as nodes and piping connecting two components as edges. Note that components may include not only process equipment but also piping branch parts and elbows, as well as piping supports that support piping. The memory unit 30 stores graph structure data for each plant to be designed, for example. The graph structure data is shared among multiple design processes and is detailed from upstream processes to downstream processes in plant design.

[0035] 4, the graph structure data GD includes a plant identifier (ID), a node list NL, and an edge list EL (not shown). The plant ID is information that uniquely identifies the plant to be designed.

[0036] The node list NL is a list of nodes included in a plant identified by a plant ID. The node list NL includes a record set for each node. Each record includes a node ID and placement position information. The node ID is information that can uniquely identify a node. The placement position information is information that indicates the placement position of a node identified by the node ID. In this embodiment, the placement position information includes an X coordinate, a Y coordinate, and a Z coordinate. The origin of the XYZ coordinate system is set in advance to a predetermined position.

[0037] The edge list EL is a list of edges included in a plant identified by a plant ID. An edge represents a connection (connection relationship) between two nodes. The edge list EL includes a record set for each edge. Each record includes an edge ID, a start node ID, an end node ID, a stream number, a line number, and attribute data.

[0038] The edge ID is information that can uniquely identify an edge. The start node ID is the node ID of the start node. Fluid flows in one direction on an edge (pipe) connecting two nodes. The start node is the node located upstream of the two nodes connected by the edge identified by the edge ID. The end node ID is the node ID of the end node. The end node is the node located downstream of the two nodes connected by the edge identified by the edge ID.

[0039] A stream number is a number assigned to a fluid flowing through an edge identified by an edge ID. The same fluid is assigned the same stream number. Because the range of stream numbers assigned is relatively large, stream numbers are not suitable for detailed management.

[0040] Line numbers are subdivisions of stream numbers and are set to provide design divisions. Line numbers are set by subdividing stream numbers, for example, from the perspective of drawing management and material management. Multiple edges are grouped, and the same line number is assigned to edges belonging to the same group. For example, multiple edges are divided into several groups based on attributes such as fluid type, design temperature, design pressure, and piping material, and the groups are divided by piping branch parts.

[0041] The attribute data is information indicating the attributes of an edge identified by the edge ID. The attribute data includes the pipe diameter (inner diameter) of the edge, as well as the composition, pressure, temperature, and required flow rate of the fluid flowing through the edge. The attribute data may also include information indicating attributes other than the pipe diameter.

[0042] The acquiring unit 21 is a functional element that acquires graph structure data from the storage unit 30 in response to an acquisition request from the terminal device 10. The acquiring unit 21 outputs the acquired graph structure data to the output unit 22.

[0043] The output unit 22 is a functional element that outputs graph structure data to the terminal device 10 that has sent the acquisition request.

[0044] The update unit 23 is a functional element that updates the graph structure data stored in the storage unit 30. The update unit 23 updates the graph structure data stored in the storage unit 30 based on output data of a design process performed in the terminal device 10 using the graph structure data.

[0045] Next, a design support method performed by the design support device 20 will be described with reference to Fig. 5. Fig. 5 is a flowchart showing an example of the design support method performed by the design support device shown in Fig. 1. The flowchart in Fig. 5 starts when the acquisition unit 21 of the design support device 20 receives an acquisition request from any of the terminal devices 10. Note that graph structure data is stored in advance in the storage unit 30.

[0046] 5, first, the acquisition unit 21 acquires graph structure data from the storage unit 30 (step S21). Then, the acquisition unit 21 outputs the acquired graph structure data to the output unit 22. Subsequently, upon receiving the graph structure data from the acquisition unit 21, the output unit 22 outputs (transmits) the graph structure data to the terminal device 10 that has sent the acquisition request (step S22).

[0047] Next, the update unit 23 determines whether or not output data has been received from the terminal device 10 (step S23). The output data is output data of the design process performed in the terminal device 10 using the graph structure data. If it is determined in step S23 that the update unit 23 has not received the output data (step S23: NO), the determination in step S23 is repeated until the update unit 23 receives the output data. If it is determined in step S23 that the update unit 23 has received the output data (step S23: YES), the update unit 23 updates the graph structure data stored in the storage unit 30 based on the received output data (step S24).

[0048] This completes the series of processes in the design support method.

[0049] Next, a series of steps in plant design will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the design process of plant design.

[0050] 6, the plant design includes a process simulation execution step PR1, a process flow diagram preparation step PR2, a plot plan design step PR3, a hydraulic calculation execution step PR4, a piping and instrumentation diagram preparation step PR5, and a three-dimensional modeling step PR6. Here, the following explanation will be given assuming that the process simulation execution step PR1, the process flow diagram preparation step PR2, the plot plan design step PR3, the hydraulic calculation execution step PR4, the piping and instrumentation diagram preparation step PR5, and the three-dimensional modeling step PR6 are performed in this order.

[0051] Each step may be performed on a different terminal device 10. Two or more steps may be performed on the same terminal device 10. Each step is performed, for example, by using a dedicated application installed on the terminal device 10.

[0052] First, a process simulation execution step PR1 is carried out. The process simulation execution step will be described in detail with reference to Fig. 7 and Fig. 8. Fig. 7 is a diagram showing an example of graph structure data after the process simulation execution step has been carried out. Fig. 8 is a diagram in which the graph structure data shown in Fig. 7 is graphed.

[0053] The process simulation execution step PR1 is a step for determining the design specifications of the main components (major equipment) for producing final products from raw materials and the design specifications of the fluids flowing through the main piping. Examples of raw materials include crude oil and raw gas. Examples of final products include refined gas, oil, and chemicals. Examples of major equipment include distillation columns, heat exchangers, and pumps. The design specifications of major equipment include the throughput, which determines the function of the major equipment. The design specifications of the fluid include the composition, pressure, and temperature.

[0054] A user of the terminal device 10 who performs the process simulation execution step PR1 starts a process simulator on the terminal device 10. The process simulator is a dedicated application for executing process simulations. Based on information about the design standards, specifications, and properties of the raw materials, the user diagrams the manufacturing process (the arrangement of major equipment and the main piping connecting the major equipment) for manufacturing a final product from the raw materials on the screen of the display device of the terminal device 10. The user may also read data from a similar past plant design as template data and diagram the major equipment and main piping based on the template data.

[0055] Then, the user causes a process simulator to execute a process simulation using the diagrammed main equipment and main piping, and determines each design parameter based on the simulation results obtained by the process simulator.

[0056] Then, when the user performs an operation on the terminal device 10 to save the determined design specifications, the terminal device 10 transmits the node IDs of the main equipment used in the process simulation, and a set of edge IDs, start node IDs, end node IDs, stream numbers, and design specifications of the fluids flowing through the main pipes set for each main pipe used in the process simulation, together with the plant ID of the plant to be designed, to the design support device 20 as output data.

[0057] Then, when the update unit 23 of the design support device 20 receives the output data from the terminal device 10, it updates the graph structure data stored in the storage unit 30. Since the storage unit 30 does not store graph structure data for the plant, the update unit 23 generates new graph structure data GD1 based on the output data and stores it in the storage unit 30.

[0058] As shown in FIG. 7, the graph structure data GD1 includes a plant ID (not shown), a node list NL1, and an edge list EL1. The node list NL1 is a list of major equipment used in the process simulation. The update unit 23 generates the node list NL1 by generating a record including a node ID for each major equipment. Each record does not include a valid value as placement position information. Note that each record may include design specifications of the major equipment as attribute data. Here, the node identified by node ID "1C-1102" is a distillation column. The node identified by node ID "1E-1105" is a heat exchanger that serves as a heat source for the distillation column. The nodes identified by node IDs "1P-1103A" and "1P-1103B" are pumps that pump out heavy components. The node identified by node ID "Bra-1" is a branching component of the piping.

[0059] The edge list EL1 is a list of the main pipes used in the process simulation. The update unit 23 generates the edge list EL1 by generating a record for each main pipe, including an edge ID, a start node ID, an end node ID, a stream number, and attribute data. Although not shown in FIG. 7, each record includes design specifications of the fluid flowing through the main pipe as attribute data. Each record does not include a valid value as a line number.

[0060] 8, the graph structure data GD1 can be expressed as a graph G1 by representing each node as a circle and each edge as a line. The graph G1 represents the topology of the plant to be designed.

[0061] In addition, if graph structure data of the plant to be designed is stored in the memory unit 30 before the process simulation execution process PR1 is performed, the process simulation may be performed using the graph structure data obtained from the design support device 20.

[0062] Specifically, in the process simulator, when a user performs an operation to read graph structure data of a plant to be designed, the terminal device 10 transmits an acquisition request including the plant ID of the plant to the design support device 20. Then, upon receiving the acquisition request from the terminal device 10, the acquisition unit 21 of the design support device 20 acquires graph structure data including the plant ID included in the acquisition request from the storage unit 30, and outputs the acquired graph structure data to the output unit 22. Then, the output unit 22 transmits the graph structure data GD1 received from the acquisition unit 21 to the terminal device 10 that transmitted the acquisition request. Then, upon receiving the graph structure data from the design support device 20, the terminal device 10 executes a process simulation based on the graph structure data.

[0063] Each time a new node record is added to the node list of the graph structure data, component data for the node is generated and registered in a database (not shown). Component data is also referred to as tag information. Component data includes, for example, a node ID and attribute data. Attribute data is information indicating the attributes of a node identified by the node ID. Component data may include design specifications of major devices as attribute data.

[0064] Next, a process flow diagram preparation step PR2 is carried out. The process flow diagram preparation step will be described in detail with reference to FIGS. 9 to 11. FIG. 9 is a diagram showing an example of a process flow diagram. FIG. 10 is a diagram showing an example of graph structure data after the process flow diagram preparation step has been carried out. FIG. 11 is a diagram showing a graph of the graph structure data shown in FIG. 10. The process flow diagram preparation step PR2 is a step of creating (preparing) a process flow diagram. In addition to the components and piping used in the process simulation, components and piping that do not need to be used for process simulation are added to the process flow diagram.

[0065] A user of the terminal device 10 who performs the process flow diagram preparation step PR2 starts a dedicated application for creating a process flow diagram on the terminal device 10. Then, when the user performs an operation to read out the graph structure data of the plant to be designed, the terminal device 10 transmits an acquisition request including the plant ID of the plant to the design support device 20.

[0066] When the acquisition unit 21 of the design support device 20 receives an acquisition request from the terminal device 10, it acquires graph structure data (here, graph structure data GD1) including the plant ID included in the acquisition request from the storage unit 30, and outputs the graph structure data GD1 to the output unit 22. Then, the output unit 22 transmits the graph structure data GD1 received from the acquisition unit 21 to the terminal device 10 that sent the acquisition request.

[0067] Then, when the terminal device 10 receives the graph structure data GD1 from the design support device 20, it displays the topology of the plant (an incomplete process flow diagram) on the display device based on the graph structure data GD1. As shown in FIG. 9, the user creates a process flow diagram by adding main piping for common fluids, main measuring instruments, and main control components (moving components) on the screen of the display device. Common fluids include heat transfer media, refrigerants, and fuel gases required for refining raw material fluids. Measuring instruments are instruments that measure flow rates, pressures, etc. Control components are components that adjust flow rates, pressures, etc. Note that cables (including wireless connections) connecting measuring instruments and control components may be treated as edges.

[0068] Then, when the user performs an operation to save the process flow diagram on the terminal device 10, the terminal device 10 transmits the node ID of the newly added node and a set of edge ID, start node ID, end node ID, and stream number set for each newly added edge as output data to the design support device 20, together with the plant ID of the plant to be designed.

[0069] Then, when the update unit 23 of the design support device 20 receives the output data from the terminal device 10, it updates the graph structure data GD1 stored in the storage unit 30 to graph structure data GD2. As shown in FIG. 10, the graph structure data GD2 includes a plant ID (not shown), a node list NL2, and an edge list EL2. For example, the update unit 23 generates a new record including the node ID of a node included in the output data and adds the record to the node list NL1 to generate the node list NL2. The update unit 23 generates a new record including a set of an edge ID, a start node ID, an end node ID, and a stream number included in the output data and adds the record to the edge list EL1 to generate the edge list EL2.

[0070] Here, for convenience of explanation, only the heat medium pipe of the heat exchanger identified by the node ID “1E-1105” is added. As shown in Fig. 11, the graph structure data GD2 can be expressed as a graph G2.

[0071] Next, the plot plan design process PR3 is carried out. The plot plan design process will be described in detail with reference to FIG. 12. FIG. 12 is a diagram showing an example of graph structure data after the plot plan design process has been carried out. The plot plan design process PR3 is a process for determining the placement positions of equipment. Therefore, new components and piping are not added in the plot plan design process PR3. The placement positions of components other than equipment may also be determined.

[0072] A user of the terminal device 10 who performs the plot plan design process PR3 starts a dedicated application for determining the placement positions of equipment on the terminal device 10. Then, when the user performs an operation to read out the graph structure data of the plant to be designed, the terminal device 10 transmits an acquisition request including the plant ID of the plant to the design support device 20.

[0073] When the acquisition unit 21 of the design support device 20 receives an acquisition request from the terminal device 10, it acquires graph structure data (here, graph structure data GD2) including the plant ID included in the acquisition request from the storage unit 30 and outputs the graph structure data GD2 to the output unit 22. Then, the output unit 22 transmits the graph structure data GD2 received from the acquisition unit 21 to the terminal device 10 that sent the acquisition request.

[0074] Then, upon receiving the graph structure data GD2 from the design support device 20, the terminal device 10 determines the placement positions of the devices based on information such as the size of each device and the connections of the piping, taking into consideration various factors such as economy, maintainability, and operability, and displays a schematic diagram showing the placement positions of the devices on a display device. For economy, for example, shortening the length of piping throughout the plant is considered. The terminal device 10 acquires information on the size of each device from a database (not shown). Then, when a user performs an operation to save the placement positions of the devices on the terminal device 10, the terminal device 10 transmits a pair of the node ID and placement position information of each device together with the plant ID of the plant to be designed as output data to the design support device 20.

[0075] Then, when the update unit 23 of the design support device 20 receives the output data from the terminal device 10, it updates the graph structure data GD2 stored in the storage unit 30 to graph structure data GD3. As shown in FIG. 12, the graph structure data GD3 includes a plant ID (not shown), a node list NL3, and an edge list EL3. For example, the update unit 23 extracts from the node list NL2 a record that includes the node ID included in the output data, and generates the node list NL3 by adding the placement position information associated with the node ID in the output data as the placement position information of the extracted record. Because the edge list EL2 is not changed, the edge list EL3 is the same as the edge list EL2.

[0076] Next, the hydraulic calculation execution step PR4 is carried out. The hydraulic calculation execution step will be described in detail with reference to FIG. 13. FIG. 13 is a diagram showing an example of graph structure data after the hydraulic calculation execution step has been carried out. The hydraulic calculation execution step PR4 is a step of determining the pipe diameter (inner diameter) required to flow the required flow rate in each pipe. Note that the length of each pipe (pipe length) is calculated in advance from the placement position of the equipment determined in the plot plan design step PR3. The pipe length may be added as attribute data of each edge.

[0077] The user of the terminal device 10 who performs the hydraulic calculation execution process PR4 starts a dedicated application for executing hydraulic calculations on the terminal device 10. Then, when the user performs an operation to read out the graph structure data of the plant to be designed, the terminal device 10 transmits an acquisition request including the plant ID of the plant to the design support device 20.

[0078] When the acquisition unit 21 of the design support device 20 receives an acquisition request from the terminal device 10, it acquires graph structure data (here, graph structure data GD3) including the plant ID included in the acquisition request from the storage unit 30 and outputs the graph structure data GD3 to the output unit 22. Then, the output unit 22 transmits the graph structure data GD3 received from the acquisition unit 21 to the terminal device 10 that sent the acquisition request.

[0079] Then, when the terminal device 10 receives the graph structure data GD3 from the design support device 20, it calculates the pipe diameter (inner diameter) required to flow the required flow rate based on the pipe length and required flow rate of each pipe included in the graph structure data GD3 (edge ​​list EL3). Then, when the user performs an operation to save the pipe diameter of the pipe on the terminal device 10, the terminal device 10 transmits a pair of the edge ID and pipe diameter of each pipe together with the plant ID of the plant to be designed to the design support device 20 as output data.

[0080] Then, when the update unit 23 of the design support device 20 receives the output data from the terminal device 10, it updates the graph structure data GD3 stored in the storage unit 30 to graph structure data GD4. As shown in FIG. 13, the graph structure data GD4 includes a plant ID (not shown), a node list NL4, and an edge list EL4. For example, the update unit 23 extracts from the edge list EL3 a record that includes the edge ID included in the output data, and generates the edge list EL4 by adding the pipe diameter associated with the edge ID in the output data as the pipe diameter of the extracted record. Since the node list NL3 is not changed, the node list NL4 is the same as the node list NL3.

[0081] Next, a piping and instrumentation diagram preparation process PR5 is carried out. The piping and instrumentation diagram preparation process will be described in detail with reference to Fig. 14 and Fig. 15. Fig. 14 is a diagram showing an example of graph structure data after the piping and instrumentation diagram preparation process has been carried out. Fig. 15 is a diagram showing the graph structure data shown in Fig. 14 in graph form. The piping and instrumentation diagram preparation process PR5 is a process of creating (preparing) a piping and instrumentation diagram.

[0082] A user of the terminal device 10 who performs the piping and instrumentation diagram preparation process PR5 starts a dedicated application for creating a piping and instrumentation diagram on the terminal device 10. Then, when the user performs an operation to read out graph structure data of the plant to be designed, the terminal device 10 transmits an acquisition request including the plant ID of the plant to the design support device 20.

[0083] When the acquisition unit 21 of the design support device 20 receives an acquisition request from the terminal device 10, it acquires graph structure data (here, graph structure data GD4) including the plant ID included in the acquisition request from the storage unit 30 and outputs the graph structure data GD4 to the output unit 22. Then, the output unit 22 transmits the graph structure data GD4 received from the acquisition unit 21 to the terminal device 10 that sent the acquisition request.

[0084] Then, when the terminal device 10 receives the graph structure data GD4 from the design support device 20, it causes the display device to display the topology of the plant (an unfinished piping and instrumentation diagram) based on the graph structure data GD4. The user creates the piping and instrumentation diagram by adding various components (piping parts) on the screen of the display device, taking into consideration maintenance, safety, control, and the like. Instead of a configuration in which the user manually adds the piping parts, the terminal device 10 may automatically add the piping parts using template data.

[0085] Then, when the user performs an operation to save the piping and instrumentation diagram on the terminal device 10, the terminal device 10 transmits the node ID of the newly added node and a set of the edge ID, start node ID, end node ID, and stream number set for each newly added edge as output data to the design support device 20, together with the plant ID of the plant to be designed.

[0086] Then, when the update unit 23 of the design support device 20 receives the output data from the terminal device 10, it updates the graph structure data GD4 stored in the storage unit 30 to graph structure data GD5. As shown in FIG. 14, the graph structure data GD5 includes a plant ID (not shown), a node list NL5, and an edge list EL5. For example, the update unit 23 generates a new record including the node ID included in the output data and adds the record to the node list NL4 to generate the node list NL5. Each record does not include a valid value as placement position information.

[0087] The update unit 23 generates an edge list EL5 by generating a new record including a set of the edge ID, start node ID, end node ID, and stream number included in the output data and adding the record to the edge list EL4. The line numbers may be assigned automatically or by the user according to, for example, preset conditions. Examples of the conditions include attributes such as the type of fluid, design temperature, design pressure, and piping material.

[0088] When an edge is split into two edges by adding a new node on the edge, the two edges inherit the stream number and attribute data of the original edge. However, the downstream edge of the two edges split by adding a reducer has a pipe diameter different from the pipe diameter of the original edge. Therefore, this edge inherits the stream number and attribute data of the original edge except for the pipe diameter. The pipe diameter of the downstream edge may be determined by hydraulic calculation in the hydraulic calculation execution step PR4, or may be determined by the nozzle size (nozzle diameter) of the equipment to which the edge is connected. After the pipe diameter of the downstream edge is determined, the determined pipe diameter may not be applicable depending on the node (e.g., equipment such as a pump) to which the edge is connected. In this case, hydraulic calculation may be performed again to change the pipe diameter of the upstream edge.

[0089] In this example, graph structure data for a portion extending from a distillation column identified by node ID "1C-1102," through a branching part identified by node ID "Bra-1," to a pump identified by node ID "1P-1103A" is shown. The node identified by node ID "FCV-001" is a flow control valve. The node identified by node ID "Gate-1" is a gate valve. The node identified by node ID "Check-1" is a check valve. The node identified by node ID "Reducer-1" is a part (reducer) that connects two pipes having different pipe diameters. As shown in FIG. 15, the above portion of graph structure data GD5 can be expressed as graph G5.

[0090] Next, a three-dimensional modeling step PR6 is carried out. The three-dimensional modeling step will be described in detail with reference to FIGS. 16 to 18. FIG. 16 is a diagram showing an example of a three-dimensional model. FIG. 17 is a diagram showing an example of graph structure data after the three-dimensional modeling step has been carried out. FIG. 18 is a diagram showing a graph of the graph structure data shown in FIG. 17. The three-dimensional modeling step PR6 is a step of determining the placement position of each component element in three-dimensional space using a three-dimensional model. In the three-dimensional modeling step PR6, parts that are not shown in the piping and instrumentation diagram, such as parts for bending pipes (elbows) and structural members for supporting pipes (pipe supports), can be added.

[0091] A user of the terminal device 10 (first terminal device) that performs the 3D modeling process PR6 starts a dedicated application for executing 3D modeling on the terminal device 10. Then, when the user performs an operation to read out graph structure data of the plant to be designed, the terminal device 10 transmits an acquisition request including the plant ID of the plant to the design support device 20.

[0092] When the acquisition unit 21 of the design support device 20 receives an acquisition request from the terminal device 10, it acquires graph structure data (here, graph structure data GD5) including the plant ID included in the acquisition request from the storage unit 30 and outputs the graph structure data GD5 to the output unit 22. Then, the output unit 22 transmits the graph structure data GD5 received from the acquisition unit 21 to the terminal device 10 that sent the acquisition request.

[0093] Then, when the terminal device 10 receives the graph structure data GD5 from the design support device 20, it acquires, from a database (not shown), 3D model data of the nodes indicated by the node IDs included in the node list NL5. Then, as shown in Fig. 16, the terminal device 10 automatically routes the pipes included in the edge list EL5 to generate a 3D model of the plant. At this time, elbows and pipe supports may be added. A user may also manually generate the 3D model on the screen.

[0094] Then, when the user performs an operation to save the three-dimensional model on the terminal device 10, the terminal device 10 transmits, as output data to the design support device 20, a set of the node ID and placement position information of the node whose placement position has been determined, and a set of the edge ID, start node ID, end node ID, and stream number set for each edge created by the newly added node, together with the plant ID of the plant to be designed.

[0095] Then, when the update unit 23 of the design support device 20 receives the output data from the terminal device 10, it updates the graph structure data GD5 stored in the storage unit 30 to graph structure data GD6. As shown in Fig. 17, the graph structure data GD6 includes a plant ID (not shown), a node list NL6, and an edge list EL6.

[0096] For example, the update unit 23 extracts from the node list NL5 a record including a node ID included in the output data, and adds the placement location information associated with the node ID in the output data as the placement location information of the extracted record. If the node list NL5 does not contain a record including the node ID included in the output data, the update unit 23 generates a record including the node ID and the placement location information associated with the node ID, and adds the record to the node list NL5. In this way, the update unit 23 generates the node list NL6.

[0097] The update unit 23 generates an edge list EL6 by generating a new record including a set of the edge ID, start node ID, end node ID, and stream number included in the output data and adding the record to the edge list EL5. Note that when a new node is added to an edge, the edge is divided into two edges, and the two edges inherit the stream number, line number, and attribute data of the original edge.

[0098] In this example, graph structure data is shown for a portion extending from a distillation column identified by node ID "1C-1102," through a branch part identified by node ID "Bra-1," to a pump identified by node ID "1P-1103A." Note that the nodes identified by node IDs "Bend-1" and "Bend-2" are elbows. As shown in FIG. 18, the above portion of graph structure data GD6 can be expressed as graph G6.

[0099] Next, a design support program P for causing a computer to function as the design support device 20 and a recording medium MD for recording the design support program P will be described with reference to Fig. 19. Fig. 19 is a diagram showing the configuration of the design support program recorded on the recording medium.

[0100] 19, the design support program P includes a main module P20, an acquisition module P21, an output module P22, and an update module P23. The main module P20 is a part that comprehensively controls the processes related to the design support. The functions realized by executing the acquisition module P21, the output module P22, and the update module P23 are the same as the functions of the acquisition unit 21, the output unit 22, and the update unit 23 in the above embodiment, respectively.

[0101] The design support program P is provided by a recording medium MD. The recording medium MD is a computer-readable non-transitory recording medium. Examples of the recording medium MD include a CD-ROM (Compact Disc Read Only Memory), a DVD-ROM (Digital Versatile Disc Read Only Memory), and a semiconductor memory. The design support program P may be provided as a data signal via a communication network NW.

[0102] In the design support system 1 and the design support device 20 described above, graph structure data that defines components provided in a plant to be designed as nodes and piping connecting two components as edges is stored in the storage unit 30. Then, in response to an acquisition request from the terminal device 10, the graph structure data is acquired from the storage unit 30 and output to the terminal device 10, and the graph structure data stored in the storage unit 30 is updated based on output data of a design process performed in the terminal device 10 using the graph structure data.

[0103] A plant can be represented by multiple components that perform a series of processes from raw materials to the final product, and piping (piping systems) that connect two components. In plant design, the granularity of the processes becomes smaller as the design progresses. Although the number of components increases accordingly, the plant can be represented throughout the plant design by multiple components and piping (piping systems) that connect two components. Therefore, by defining the components installed in the plant as nodes and the piping (piping systems) that connect two components as edges, graph-structured data can be shared among multiple design processes without preparing data individually for each design process. This allows the graph-structured data to be gradually refined from upstream processes to downstream processes in the plant design. This results in improved plant design efficiency.

[0104] The update unit 23 adds attribute data of nodes included in the graph structure data stored in the storage unit 30 to the graph structure data. In plant design, attributes such as the placement position of nodes are determined in several design processes. According to the above update process, output data of such design processes can be reflected in the graph structure data.

[0105] The update unit 23 adds attribute data of edges included in the graph structure data stored in the storage unit 30 to the graph structure data. In plant design, attributes such as pipe diameters of edges are determined in several design processes. According to the above update process, output data of such design processes can be reflected in the graph structure data.

[0106] The update unit 23 adds edges to the graph structure data stored in the storage unit 30. In a plant, common fluids such as heat transfer media, refrigerants, and fuel gases are used to refine raw material fluids, and piping is used to carry the common fluids. In this way, piping may be added in some design processes. The above update process allows the output data of such design processes to be reflected in the graph structure data.

[0107] The update unit 23 adds a node to the graph structure data stored in the storage unit 30, and adds an edge connecting the added node to another node. As described above, in plant design, the granularity of the process becomes smaller as the design progresses. Accordingly, components are added, and piping connected to the added components is added. The above update process allows the output data of such design processes to be reflected in the graph structure data.

[0108] The terminal device 10 that performs 3D modeling uses the graph structure data to display a 3D model of the plant to be designed on a display device. Therefore, the plant is visualized, allowing the user to easily recognize the arrangement of each component and each pipe of the plant.

[0109] The design support apparatus and design support system according to the present disclosure are not limited to the above-described embodiments.

[0110] For example, the design support device 20 may be configured by a single device that is physically or logically coupled, or may be configured by multiple devices that are physically or logically separated from each other. For example, the design support device 20 may be realized by multiple computers distributed over a communication network NW, such as in cloud computing.

[0111] When a physical piping component is added in the 3D modeling step PR6, the piping diameter of the edge in the edge lists EL1 to EL5 may represent the inner diameter of the piping system, rather than the inner diameter of the physical piping component. Note that the piping diameter is not limited to the inner diameter, but may be the outer diameter, nominal diameter, or the like. Furthermore, if the piping system includes components with multiple diameters, the piping diameter may be a representative diameter.

[0112] Piping (piping components) are components (plant equipment) installed in a plant, and therefore may be treated as nodes. Similarly, cables (including wireless connections) connecting measuring equipment and control components may be treated as nodes. In this case, the connection between two components is treated as an edge. In other words, the graph structure data may be data that defines all components installed in a plant, including piping, as nodes, and the connection between two components as an edge.

[0113] In the three-dimensional modeling step PR6, a piping component is added. Therefore, as shown in Fig. 20, in the node list NL6A of the graph structure data GD6A, a record including the node ID of the piping and placement position information associated with the node ID is further added to the node list NL6 of the graph structure data GD6. In the edge list EL6A of the graph structure data GD6A, a record including the node ID of the piping as a start node ID or an end node ID is further added to the edge list EL6 of the graph structure data GD6.

[0114] Note that the nodes identified by the node IDs "Pipe-1" and "Pipe-2" are pipes (piping components). Pipes do not necessarily exist between two components other than pipes. The presence or absence of a pipe is determined according to the layout. For example, two valves may be directly connected to each other, or two valves may be connected via a pipe. As shown in FIG. 21, the above portion of the graph structure data GD6A can be expressed as a graph G6A.

[0115] A plant can also be represented by multiple components, including piping, for carrying out a series of processes from raw materials to obtaining a final product, and the connection relationships between two components. As described above, in plant design, although the number of components increases as the design progresses, the plant can be represented throughout the plant design by multiple components and the connection relationships between two components. Therefore, by defining the components installed in the plant as nodes and the connection relationship between two components as edges, graph-structured data can be shared among multiple design processes without preparing data individually in each design process, and the graph-structured data can be gradually refined from upstream processes to downstream processes in the plant design. As a result, the efficiency of plant design can be improved. [Explanation of symbols]

[0116] 1...design support system, 10...terminal device (first terminal device), 20...design support device, 21...acquisition unit, 22...output unit, 23...update unit, 30...storage unit.

Claims

1. A design support device that supports plant design including a plurality of design processes, a storage unit that stores graph structure data in which components provided in a plant to be designed are defined as nodes and a connection relationship between two components is defined as an edge; an acquisition unit that acquires the graph structure data from the storage unit in response to an acquisition request from a terminal device that performs each of the plurality of design processes; an output unit that outputs the graph structure data to the terminal device; an updating unit that updates the graph structure data stored in the storage unit based on output data of a design process performed by each application using the graph structure data in the terminal device; Equipped with The graph structure data is shared by different applications among the plurality of design processes and is detailed from an upstream process to a downstream process of the plant design.

2. the graph structure data includes a node list that is a list of a plurality of nodes included in the plant, and an edge list that is a list of a plurality of edges included in the plant; The design support device according to claim 1 , wherein the update unit refines the graph structure data by updating the node list and the edge list based on the output data.

3. the edge list includes a record set for each of the plurality of edges; 3. The computer aided design system according to claim 2, wherein the record includes identifiers of two nodes whose connection relationship is defined by the edge.

4. 4. The computer-aided design system according to claim 2, wherein the plurality of edges are grouped according to attributes of a fluid flowing through the edges.

5. the node is a process device; 4. The design support device according to claim 1, wherein the edge is a pipe.

6. 4. The design support device according to claim 1, wherein the update unit adds attribute data of nodes included in the graph structure data to the graph structure data stored in the storage unit.

7. 4. The design support device according to claim 1, wherein the update unit adds attribute data of edges included in the graph structure data to the graph structure data stored in the storage unit.

8. 4. The design support device according to claim 1, wherein the update unit adds an edge to the graph structure data stored in the storage unit.

9. 4. The design support device according to claim 1, wherein the update unit adds a node to the graph structure data stored in the storage unit, and adds an edge connecting the added node to another node.

10. 4. The design support device according to claim 1, wherein the plurality of design processes include a process flow design process, a plot plan design process, a piping and instrumentation design process, and a three-dimensional modeling process.

11. The design support device according to any one of claims 1 to 3, a plurality of terminal devices; Equipped with A design support system in which each of the plurality of terminal devices performs one of the plurality of design processes.

12. the plurality of terminal devices includes a first terminal device that performs three-dimensional modeling of the plurality of design processes, The design support system according to claim 11 , wherein the first terminal device uses the graph structure data to display a three-dimensional model of the plant on a display device.

Images