JP6905389B2 - Plant design equipment, plant design methods, and plant design programs - Google Patents

Description

Embodiments of the present invention relate to plant design equipment, plant design methods, and plant design programs.

Generally, power plant design is performed for each design field such as piping system design, electrical system design, and instrumentation control design. At this time, since it is necessary to confirm the consistency of data between these fields, the design is performed in order for each design field. Therefore, if the design of one field is stopped, the design of another field cannot be started, and if the design of one field is changed, the other fields that have already been designed are also affected, and the design of the power plant is quick. It may not proceed to. Therefore, there is a demand for a method that can quickly proceed even if the design of the power plant is performed for each design field. Furthermore, how to manage the identification information of the device between different design fields becomes a problem.

Japanese Unexamined Patent Publication No. 2013-61944

An object of the present invention is to provide a plant design apparatus, a plant design method, and a plant design program capable of rapidly designing a plant (power plant, chemical plant, etc.).

According to one embodiment, the plant design apparatus includes a management unit that manages identification information of equipment in the power plant. The apparatus further includes an acquisition unit that acquires information on equipment in the power plant from a first to Nth (N is an integer of 2 or more) database. The device is further _{obtained from information obtained from the K 1} (K ₁ is an integer from 1 to N) database and from a K ₂ (K ₂ is an integer from 1 to N) database _{different from the K 1 database.} and information, by associating with the identification information includes a creation unit that creates display data for displaying the information of devices in the power plant, the creation unit, and the information from the first K ₁ database , information from the first K ₂ database whether overlap, the decision on the identification information, the created display data on the basis of the overlapping of the determination result.

It is a schematic diagram which shows the structure of the plant design system of 1st Embodiment. It is a figure which showed the example of the tag number of 1st Embodiment. It is a figure which showed the example of the mutual cooperation between the databases of 1st Embodiment. It is a flow chart which shows an example of the plant design method of 1st Embodiment. It is a figure which shows the 1st operation example of the plant design apparatus of 1st Embodiment. It is a figure which showed the system diagram, the device diagram, and the example of a single connection of 1st Embodiment. It is a figure which shows the 2nd operation example of the plant design apparatus of 1st Embodiment. It is a figure which showed the example of the layout drawing of 1st Embodiment. It is a figure which shows the 3rd operation example of the plant design apparatus of 1st Embodiment. It is a schematic diagram for demonstrating the data linkage in 1st Embodiment. It is a schematic diagram for demonstrating the data linkage in 2nd Embodiment. It is a figure for demonstrating the information model in 2nd Embodiment. It is a table for demonstrating the information model in 2nd Embodiment. It is a flow chart which shows the operation example of the plant design apparatus of 2nd Embodiment. It is a schematic diagram which shows the structure of the plant design system of 2nd Embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

(First Embodiment)
FIG. 1 is a schematic diagram showing the configuration of the plant design system of the first embodiment.

The plant design system of FIG. 1 includes a plant design device 1, a plurality of databases (DB) 2, a plurality of terminal devices 3, and a communication network 4 such as a LAN (Local Area Network) that connects them to each other. There is. FIG. 1 shows five databases 2a to 2e as an example of a plurality of databases 2 and three terminal devices 3a to 3c as an example of a plurality of terminal devices 3. These databases 2 are examples of first to Nth databases (N is an integer of 2 or more).

In the present embodiment, the design of the power plant is performed for each design field such as piping system design, electrical system design, and instrumentation control design, and is performed using, for example, the terminal device 3. The design-related information created by the terminal device 3 is stored in the database 2. The database 2 of this embodiment is prepared for each design field and purpose of use.

For example, the database 2a is used for piping system design, the database 2b is used for electrical system design, and the database 2c is used for instrumentation control design. These databases 2a to 2c are examples of databases by design field. The database 2d is a CAD database that stores CAD (Computer Aided Design) drawings for designing a power plant and list information for CAD. The database 2e is a specification information database that stores specification information of equipment in the power plant. Examples of the specification information database include a module DB that stores information for each module such as valves and motors, a component DB that stores information for each component that combines multiple modules, and information for each power plant. Examples include a digital plant DB. Examples of other databases will be described later (see, for example, FIG. 4).

The plant design device 1 is a device that performs various processes related to the design of a power plant, and for example, manages a database 2 and simulates the operation of a power plant. The plant design device 1 includes a control unit 11 such as a processor and a control circuit, an input / output unit 12 such as a keyboard, a mouse, and a display, a storage unit 13 such as a memory and a storage, and a communication unit 14 such as a communication interface. ing.

The control unit 11 includes functional blocks such as a management unit 11a, an acquisition unit 11b, a detection unit 11c, an update unit 11d, a simulation unit 11e, a creation unit 11f, and a display unit 11g. These functional blocks are realized, for example, by executing the computer program stored in the storage unit 13 by the control unit 11. This program is an example of a plant design program, and may be installed in the plant design device 1 from a recording medium, or may be downloaded to the plant design device 1 from a server or the like on the communication network 4.

The management unit 11a manages the identification information of the equipment in the power plant to be designed. Examples of equipment are the modules and components described above, such as various tanks, pumps, coolers, valves, filters, bearings, transformers, blowers, motors and the like. An example of identification information is an ID (identification) code of each device. The management unit 11a of the present embodiment manages tag numbers such as RDS-PP (registered trademark: Reference Designation System for Power Plants) as identification information of each device.

FIG. 2 is a diagram showing an example of a tag number of the first embodiment.

In FIG. 2, the management unit 11a manages each device by a tag number, and each database 2 manages each device by a unique ID code. FIG. 2 shows the correspondence between the tag number of the management unit 11a and the ID code of each database 2.

For example, the tag number "ID0001" represents the tag number of the main oil pump A in the power plant. The main oil pump A is managed by the piping system DB (database 2a) with the ID code "P0001-02", the electrical system DB (database 2b) is managed by the ID code "E0004-07", and the instrumentation control DB (instrumentation control DB). Database 2c) is managed by the ID code "C0021-10".

The management unit 11a manages a list showing the correspondence between the tag number of the management unit 11a and the ID code of each database 2. Therefore, when the plant design device 1 refers to this list, the information of a certain device stored in a certain database 2 and the information of another device stored in another database 2 are the same device. It is possible to determine whether the information is the information of the above or the information of a different device. By using this, the plant control device 1 can link the information between the databases 2 with each other. Details of such cooperation will be described later.

The list in FIG. 2 is called a mutual cooperation list because it is a list for linking information between databases 2 to each other. The tag number and the mutual cooperation list of the present embodiment are stored and managed in the storage unit 13.

FIG. 10 is a schematic diagram for explaining the data linkage in the first embodiment.

As described above, the design data (plant design data) of the power plant of the present embodiment is stored in a plurality of databases 2. In FIG. 10, the plant design data includes the database 2a (hereinafter, also referred to as “first DB2a”), the database 2b (hereinafter, also referred to as “second DB2b”), and the database 2c (hereinafter, also referred to as “third DB2c”). It shows how it is stored in.

When storing the plant design data in these databases 2, any method may be used to classify which data is stored in which database 2. For example, the data may be divided by plant, by drawing, or by design department. Further, the same data may be stored in a plurality of databases 2 in duplicate.

Hereinafter, an example in which the plant design data is divided for each drawing and stored in the database 2 will be described.

The first DB2a stores the device type, name, unique number (ID), and the like as information on the system diagram of the plant. In the second DB 2b, the unique number, name, coordinates, installation direction, etc. of the equipment are stored as information regarding the layout drawing of the plant. The third DB2c stores equipment unique numbers, capacities, names, wiring information, and the like as information related to the single-line connection diagram of the plant.

In this case, the names of the same devices may be different from each other among the plurality of databases 2. For example, the name of a certain pump may be set to "pump 1" in the first DB2a and "pump 1A" in the second DB2b. It should be noted that it can be determined that the pump 1 and the pump 1A are the same pump by using the tag number of the management unit 11a.

The plant design device 1 can extract and search the data stored in each database 2. Examples of the extraction / search method include narrowing down based on targets, narrowing down individuals, and narrowing down based on processing. The extraction and search processes are performed by the acquisition unit 11b.

In target-based narrowing, the data to be extracted and the data to be searched are narrowed down based on the information about the elements and parts of the plant. Examples of information about plant elements and parts are pump and valve IDs, names, installation locations, and the like. Examples of information about the installation location are the installation location ID, name, type, coordinates, range, and the like.

In the narrowing down of individuals, the data to be extracted and the data to be searched are narrowed down based on the matching of the attributes of the individuals and the matching of the relationships of the individuals. The consistency of attributes can be determined by using, for example, ID, name, type, type, specification, and the like. The consistency of the relationship can be determined by using, for example, the configuration, the connection destination, the adjacent device, and the like.

In the processing-based narrowing down, the data to be extracted and the data to be searched are narrowed down based on the information related to the data processing. For example, data updated after a certain date or data based on the latest approval result is narrowed down.

The plant design device 1 creates an aggregate of data based on the extraction results and search results of data from one or more databases 2. In FIG. 10, the data from the first DB2a is shown by the circle D1, the data from the second DB2b is shown by the circle D2, and the data from the third DB2c is shown by the circle D3.

In the present embodiment, as described above, the same data may be duplicated and stored in a plurality of databases 2. Therefore, the data from the first DB2a, the data from the second DB2b, and the data from the third DB2c may overlap with each other. The overlap of the circles D1 to D3 in FIG. 10 schematically shows this. In this case, even if the names of the same devices are different between the databases 2, such that the name of a certain pump is set to "pump 1" in the first DB2a and "pump 1A" in the second DB2b. good. The collection of data represented by the circles D1 to D3 is created by the creation unit 11f.

The plant design device 1 filters an aggregate of data by a filter, and displays the filtered data on the display (input / output unit 12) of the plant design device 1 or the display of the terminal device 3. The filter may or may not integrate duplicate attributes. For example, if the aggregate of data includes the data of "pump 1" acquired from the first DB2a and the data of "pump 1A" acquired from the second DB2b, the pump 1 and the pump 1A point to the same pump. Therefore, the former data and the latter data belong to the overlapping region of the circles D1 and D2 (see the shaded region in FIG. 10). In this case, the plant design device 1 may display only the data of the "pump 1" acquired from the first DB 2a, or may display only the data of the "pump 1A" acquired from the second DB 2b. Alternatively, both the former data and the latter data may be displayed. It can be determined from the tag number of the management unit 11a that the pump 1 and the pump 1A are the same pump. The data filtering is performed by the creation unit 11f, and the data display is performed by the display unit 11g.

As described above, according to the data linkage of FIG. 10, it is possible to suppress the inconvenience when the data of the same device is duplicatedly stored in the plurality of databases 2. For example, even if designers in different fields store the data of the same device in different databases 2, it is possible to avoid data inconsistencies and the designers can recognize the existence of data duplication. These databases 2 (the _{K 1} and _{K 2} of 1 to N is an integer) the _{K 1} and the _K 2 is an example of a database.

When the plant design device 1 displays both the data of "pump 1" acquired from the first DB2a and the data of "pump 1A" acquired from the second DB2b, the unit system and data of both data are displayed on the filter. The types may be unified. This is the same not only when displaying the data of the same device from the plurality of databases 2 but also when displaying the data of different devices from the plurality of databases 2.

Further, the plant design device 1 may display the filtered data in the form of, for example, a table or a graph. In this case, if the data of an item having a table or graph is not included in the filtered data, the plant design apparatus 1 may display that the data of this item is insufficient. Examples of such tables and graphs are List 27 (FIG. 5) and Engineering List 32 (FIG. 7), which will be described later.

FIG. 5 is a diagram showing a first operation example of the plant design device 1 of the first embodiment. FIG. 6 is a diagram showing an example of the system diagram 21, the device diagram 23, and the single connection 25 of the first embodiment.

FIG. 5 shows an example in which the list 27 is created by adding the information of the device FIG. 23 and the information of the unit 25 to the device list 22 obtained from the information of the system diagram 21, and the list 27 is displayed. There is. The list table 27 is created by the creation unit 11f, and is displayed on the display (input / output unit 12) of the plant design device 1 and the display of the terminal device 3 by the display unit 11g. Examples of the system diagram 21, the equipment diagram 23, and the single connection 25 are shown in FIGS. 6 (a), 6 (b), and 6 (c), respectively.

The details of FIG. 5 will be described below.

The information in the system diagram 21, the information in the equipment diagram 23, and the information in the unit 25 are information about the power plant to be designed, and are stored in the corresponding databases 2. The information of the system diagram 21, the information of the device diagram 23, and the information of the single connection 25 are acquired from these databases 2 by the acquisition unit 11b, and are used by the creation unit 11f and the display unit 11g. Reference numeral 24 indicates a list of information relating to the device diagram 23, and reference numeral 26 indicates a list of information relating to the unit 25. The information of the system diagram 21, the information of the device diagram 23, and the information of the single connection 25 can be edited by using the terminal device 3. These databases 2 (the _{K 1} and _{K 2} of 1 to N is an integer) the _{K 1} and the _K 2 is an example of a database.

The device list 22 is information corresponding to the line of the list 27, as indicated by reference numeral L1. The row of the list table 27 indicates the equipment in the power plant to be designed by the tag number managed by the management unit 11a. On the other hand, the information in the device diagram 23 and the information in the single connection 25 are information corresponding to the columns in the list 27, as indicated by reference numerals L2 and reference numeral L3.

In this example, first, in the system diagram 21, the devices related to the electric load are listed, and the device list 22 is created. Examples of equipment related to electrical load are electric valves, pumps and control panels, and examples of equipment not related to electrical load are manual valves (see FIG. 5). Next, the capacity and voltage are specified in the display items of the list 27 from the device diagram 23. Further, the load capacity and the rated voltage of the single unit 25 are specified in the display items of the list 27. After that, the numerical data constituting the list 27 is acquired from the database 2 of the system diagram 21, the database 2 of the device diagram 23, and the database 2 of the unit 25, and the list 27 is created. These processes are performed by the creating unit 11f.

According to this list 27, it is possible to compare whether or not the capacity and voltage of the equipment diagram 23 match the load capacity and rated voltage of the single unit 25 for the equipment related to the electric load of the system diagram 21. It will be possible. The arrow L4 indicates that the capacity of the device FIG. 23 corresponds to the load capacity of the single unit 25 with respect to the device “10MDG10 EP010”. The creating unit 11f may display a display column in which the capacity and voltage of the device diagram 23 and the load capacity and rated voltage of the single unit 25 do not match with a color different from other display columns.

FIG. 7 is a diagram showing a second operation example of the plant design device 1 of the first embodiment. FIG. 8 is a diagram showing an example of the layout drawing 33 of the first embodiment.

FIG. 7 shows an example in which the engineering screen 31 is displayed using the above-mentioned system diagram 21 and the engineering data list 32 is acquired. The engineering screen 31 and the engineering list 32 are created by the creation unit 11f, and are displayed on the displays of the plant design device 1 and the terminal device 3 by the display unit 11g. Information necessary for the engineering screen 31 and the engineering list 32 is acquired from each database 2 by, for example, the acquisition unit 11b.

In this example, first, a device is selected from the system diagram 21 as shown by reference numeral E1 in FIG. 7 (a). For example, a pump and equipment that affects the pump are selected. Each device is managed by the tag number of the management unit 11a.

Next, as shown by reference numeral E2 in FIG. 7B, the icon of the selected device is copied from the system diagram 21 to the engineering screen 31. At this time, the attribute information of each device is copied together. Therefore, even on the engineering screen 31, it is possible to create and display a list of devices existing on the engineering screen 31. This list may be the same as the above-mentioned device list 22.

Next, as shown by reference numeral E3 in FIG. 7C, the operator of the engineering screen 31 manually connects the devices on the engineering screen 31 to each other. This connection may be made automatically by the creating unit 11f, or may be made manually by the operator based on the presentation of the connection from the creating unit 11f.

Next, the engineering list (list) 32 is created by adding the information of the device diagram 23 and the information of the layout diagram 33 to the device list 22 obtained from the information of the system diagram 21, and the engineering list 32 is displayed ( FIG. 7 (d)). See FIG. 8 for an example of layout diagram 33. The information in the layout diagram 33 is information regarding the layout of the equipment in the power plant to be designed, and is stored in the corresponding database 2. The information in the layout drawing 33 is acquired from the database 2 by the acquisition unit 11b and used by the creation unit 11f and the display unit 11g. Reference numeral 34 indicates a list of information regarding the layout drawing 33. The information in the layout diagram 33 can be edited by using the terminal device 3 in the same manner as the information in the system diagram 21 and the information in the equipment diagram 23. The database 2 is also an example of the _{K 1} and the _{K 2} database.

The device list 22 is reflected in the portion indicated by the reference numeral V1 in the engineering list 32. The information in the layout drawing 33 is reflected in the portion indicated by reference numeral V2 in the engineering list 32. The information in the equipment diagram 23 is reflected in the portion indicated by the reference numeral V3 in the engineering list 32. Then, the numerical data of the portion indicated by the reference numeral V2 and the reference numeral V3 can be obtained from the layout drawing 33 and the device diagram 23, and can also be obtained by performing numerical calculation or simulation on the device on the engineering screen 31 of FIG. 7 (c). .. These numerical calculations and simulations are performed by, for example, the simulation unit 11e. The information in the engineering list 32 is stored in, for example, the storage unit 13 or the database 2.

According to the engineering list 32, it is possible to design the equipment (here, the pump) in the power plant by using the plurality of databases 2.

FIG. 3 is a diagram showing an example of mutual cooperation between the databases 2 of the first embodiment.

A database for each design field such as a piping system DB, an electric system DB, and an instrumentation control DB stores characteristic information of equipment in a power plant in association with a hierarchical structure of equipment. FIG. 3 shows an example of a hierarchical structure in the piping system DB and a hierarchical structure in the electric system DB. For example, characteristic information such as the model, discharge amount, discharge pressure, and suction / discharge port diameter of the main oil pump A is stored in the layer of the "main oil pump A" of the piping system DB. The ID code P0001-02 is further stored in the layer of "main oil pump A" in the piping system DB.

As described above, the "main oil pump A" of the piping system DB corresponds to the "main oil pump A" of the electric system DB. Therefore, the plant control device 1 mutually links the characteristic information of the "main oil pump A" in the piping system DB and the characteristic information of the "main oil pump A" in the electric system DB. Specifically, when one characteristic information is changed, the other characteristic information is also updated in the same manner. Such processing is performed by the acquisition unit 11b, the detection unit 11c, and the update unit 11d.

The characteristic information in the database 2 can be changed in a design process using the terminal device 3. For example, when the piping system is designed using the terminal device 3 and the design of the main oil pump A is changed, the result is stored in the piping system DB and the characteristic information of the main oil pump A in the piping system DB is changed. Will be done. In this case, the plant control device 1 automatically updates the characteristic information of the main oil pump A in the electric system DB by mutual cooperation.

Hereinafter, the processing of the acquisition unit 11b, the detection unit 11c, and the update unit 11d will be described with reference to FIG. 1 again.

The acquisition unit 11b acquires characteristic information of the equipment in the power plant from each database 2 via the communication network 4. The acquisition unit 11b may acquire the characteristic information by push-type communication, or may acquire the characteristic information by pull-type communication.

The detection unit 11c detects a change in the characteristic information in each database 2. Any method may be used to detect the change in the characteristic information. For example, regarding the characteristic information of the main oil pump A in the piping system DB, if the last change time of this characteristic information is later than the time when the detection unit 11c last accessed this characteristic information, it is said that this characteristic information has been changed. Can be detected. Further, when the characteristic information of the main oil pump A in the piping system DB is changed, the notification may be transferred from the piping system DB to the detection unit 11c.

The update unit 11d performs a process of linking the characteristic information of the databases 2 with each other. Specifically, when the predetermined characteristic information of the device having the predetermined identification information is changed in the database X, the update unit 11d describes the device having the predetermined identification information in another database Y. Update predetermined characteristic information. Database X is an example of the Xth database (X is an integer from 1 to N), and database Y is an example of the Yth database (Y is an integer from 1 to N). The update by the update unit 11d is performed via the communication network 4.

For example, assume that the model of the main oil pump A is changed from "A1" to "A2" in the piping system DB. According to the mutual cooperation list, the main oil pump A (P0001-02) in the piping system DB has the tag number "ID0001", and similarly, the main oil pump A (E0004-07) in the electric system DB also has. , Has a tag number "ID0001". Therefore, the update unit 11d updates the model of the main oil pump A from "A1" to "A2" in the electric system DB. In this case, the tag number "ID0001" is an example of predetermined identification information, and the model of the main oil pump A is an example of predetermined characteristic information. When updating the characteristic information of the main oil pump A of the electric system DB, the updating unit 11d may update only the model, or collectively update the model, the discharge amount, the discharge pressure, and the suction / discharge port diameter. You may. The update unit 11d acquires the characteristic information of the main oil pump A of the piping system DB from the acquisition unit 11b, and uses this characteristic information to update the characteristic information of the main oil pump A of the electric system DB.

In this way, in the update unit 11d, the content of the updated characteristic information of the main oil pump A in the electric system DB is the same as the content of the changed characteristic information of the main oil pump A in the piping system DB. To update. Therefore, even if the designer of the piping system design changes the characteristic information of the main oil pump A, it is possible to avoid the inconsistency of the characteristic information between the piping system DB and the electric system DB.

When the characteristic information in the piping system DB is changed, the update by the update unit 11d is also performed in the database 2 other than the electrical system DB. For example, when the characteristic information of the main oil pump A is changed in the piping system DB, each database 2 in which the characteristic information of the main oil pump A is stored is updated. According to the mutual cooperation list of FIG. 2, when the characteristic information of the main oil pump A (P0004-02) is changed in the piping system DB, the characteristics of the main oil pump A (C0021-10) in the instrumentation system DB. Information is also updated.

The update by the update unit 11d is also applied to the CAD database (database 2d). For example, when the CAD drawing or list information in the CAD database is changed, the corresponding characteristic information in the other database 2 is also automatically updated. Further, when one of the CAD drawing and the list information in the CAD database is changed, the update unit 11d may automatically update the other as well.

The simulation unit 11e acquires the characteristic information of the equipment in the power plant from each database 2, and uses this characteristic information to simulate the operation of the power plant. The design of the power plant of this embodiment is performed for each design field such as piping system design, electrical system design, and instrumentation control design, and it is confirmed by this simulation whether or not the data between these fields are consistent. It is possible to do. The plant design device 1 may have a function of confirming the consistency of data between these fields by a method other than simulation.

FIG. 4 is a flow chart showing an example of the plant design method of the first embodiment.

First, from the purchase specifications, a digital plant corresponding to the power plant to be designed is constructed (steps S1 and S2). Information about the digital plant is stored in the digital plant DB.

Next, in step S3, the design of this power generation plant is changed into heat balance design (step S3a), piping system design (step S3b), equipment basic design (step S3c), electrical system design (step S3d), and instrumentation control design. (Step S3e), overall process design (step S3f), and so on for each design field. Information on each of these designs is stored in the corresponding design field database. For example, information on the piping system design, the electrical system design, and the instrumentation control design is stored in the above-mentioned piping system DB, electrical system DB, and instrumentation control DB, respectively.

At this time, the design of the power plant of the present embodiment is executed in parallel for a plurality of design fields using these design field-specific databases (step S3). For example, the electrical system design can also be performed during the execution of the piping system design.

As described above, the update unit 11d performs a process of linking the characteristic information of the databases 2 with each other. For example, when the model of the main oil pump A is changed from "A1" to "A2" in the piping system DB, the update unit 11d changes the model of the main oil pump A from "A1" to "A2" in the electrical system DB. Update. Therefore, even if the designer of the piping system design changes the characteristic information of the main oil pump A, it is possible to prevent the characteristic information from being inconsistent between the piping system DB and the electrical system DB. Therefore, in the present embodiment, even if the design of the power plant is executed in parallel for a plurality of design fields, it is possible to avoid inconsistency of the characteristic information between the databases for each design field. Therefore, in step S3 of the present embodiment, by adopting such a parallel design, the efficiency and optimization of the design work are aimed at.

After that, in this method, after undergoing detailed design of the power plant, shipping inspection, on-site installation / construction, and trial run (steps S4 to S7), the operation of the power plant is started (step S8). The information related to steps S4 to S7 is stored in the corresponding database 2.

FIG. 9 is a diagram showing a third operation example of the plant design device 1 of the first embodiment.

In the examples of FIGS. 5 and 7, it is assumed that the same device (for example, a tag number) is attached to the same device in all the related databases 2. However, not all databases 2 of the plant design system have the same key attached to the same equipment. In the example of FIG. 9, as shown in FIG. 9A, a case where the device diagram 23 and the BOM (Bill of Material) 41 are connected by a key called “name” will be considered.

The information of BOM 41 is information on the business partner, delivery date, model, price, efficiency, etc. of the equipment in the power plant to be designed, and is stored in the corresponding database 2. The information of the BOM 41 is acquired from the database 2 by the acquisition unit 11b, and is used by the creation unit 11f and the display unit 11g. Reference numeral 42 indicates a list of information regarding BOM 41. The information of the BOM 41 can be edited by using the terminal device 3 in the same manner as the information of the system diagram 21, the information of the device diagram 23, and the information of the layout diagram 33. The database 2 corresponding to BOM 41 is an example of the K ₃ (K ₃ is an integer from 1 to N) database.

As explained with reference to FIG. 4, in the plant design method of the present embodiment, the data is delivered along the business flow, so that the correspondence relationship between the own data and the partner's data is determined at the time of data delivery. Need to show. Here, consider the case where the "name" of each device is used as a key at the time of delivery.

FIG. 9B shows a setting screen 43 for setting the keys. On the setting screen 43, it is possible to perform an operation of associating the name of a certain device on the device FIG. 23 with the name of a certain device on the BOM 41. The setting result on the setting screen 43 is saved by the management unit 11a in the form of "device diagram.name = BOM.name". The setting screen 43 is created by the creation unit 11f, and is displayed on the display of the plant design device 1 or the terminal device 3 by the display unit 11g.

FIG. 9C shows how the device FIG. 23 and the BOM 41 are connected by a key called “name” according to the setting result on the setting screen 43. Further, in FIG. 9C, the system diagram 21 and the device diagram 23 are already connected by a key called “tag number”. Therefore, these keys make it possible to link the information in the system diagram 21, the device diagram 23, and the database 2 of the BOM 41 with each other. This "name" is an example of the second identification information.

FIG. 9D shows a list 44 similar to the list 27 in FIG. However, this list 44 is created by using the information of the system diagram 21 indicated by the reference numeral K1, the information of the device diagram 23 indicated by the reference numeral K2, and the information of the BOM 41 indicated by the reference numeral K3. When creating the list 44, the information of a certain device on the system diagram 21 and the information of a certain device on the device diagram 23 are associated with each other by using a tag number. On the other hand, the information of a certain device on the device FIG. 23 and the information of a certain device on the BOM 41 are associated with each other by using a name. As a result, the information of the same device can be arranged in the same line on the list 44. The list 44 is created by the creating unit 11f and displayed on the display of the plant design device 1 or the terminal device 3 by the display unit 11g.

According to this list 44, it is possible to compare whether or not the capacity and voltage of the equipment diagram 23 match the capacity and voltage of the BOM 41 for the equipment related to the electric load of the system diagram 21. The arrow K4 indicates that the capacity of the device FIG. 23 matches the capacity of the BOM 41 with respect to the device “10MAG30 EP010”.

As described above, the plant design device 1 of the present embodiment manages the tag number which is the identification information of the equipment in the power plant, and uses the tag number to mutually link the characteristic information of the databases 2. This makes it possible to execute the design of a power plant in parallel for a plurality of design fields.

Further, even if the design information in these fields is stored in separate databases 2, inconsistency of the design information between the databases 2 and inconveniences when using the database 2 can be avoided, so that the design information is distributed to a plurality of databases 2. Can be managed. As a result, it is possible to reduce the time required to refer to the information from the database 2 and reduce the amount of information stored in each database 2. Furthermore, designers in each field can easily recognize such duplications and automatically recognize such duplications without being overly aware of the duplications and inconsistencies with the work of designers in other fields. It becomes possible to avoid it.

Further, the plant design device 1 of the present embodiment creates and displays a table including information from a plurality of databases 2 by using tag numbers. This makes it possible to easily perform a design using a plurality of databases 2. Further, in the present embodiment, by using the tag number and other keys (for example, names) together, it is possible to easily perform a design using more databases 2.

These actions can contribute to shortening the design time of the power plant. Therefore, according to the present embodiment, it is possible to quickly design a power plant.

(Second Embodiment)
FIG. 11 is a schematic diagram for explaining the data linkage in the second embodiment. Since the content shown in FIG. 11 is a modification of the content shown in FIG. 10, FIG. 11 will be mainly described with respect to the difference from FIG.

The plant design data of the present embodiment is stored in a plurality of databases 2 as in the first embodiment. At this time, the plant design data is stored according to the information model, which is a rule for storing equipment information. The information model is common between these databases 2. The details of the information model will be described later. FIG. 11 shows how the plant design data is stored in the first DB2a, the second DB2b, and the third DB2c according to the information model.

The plant design device 1 can extract and search the data stored in each database 2. Then, the plant design device 1 creates an aggregate of data based on the extraction results and search results of data from one or more databases 2. In FIG. 11, the data from the first to third DB2a to 2c are shown by circles D1 to D3, respectively. The overlap of the circles D1 to D3 in FIG. 11 schematically shows that the data from the first to third DB2a to 2c can overlap with each other.

The plant design device 1 integrates a collection of data based on the integration conditions, and displays the integrated data on the displays of the plant design device 1 and the terminal device 3. For example, when the aggregate of data includes the data of "pump 1" acquired from the first DB2a and the data of "pump 1A" acquired from the second DB2b, the plant design apparatus 1 obtains "pump 1A" from the first DB2a. The data of "Pump 1" and the data of "Pump 1A" acquired from the second DB 2b are integrated based on the integration conditions, and the integrated data is displayed. The data integration is performed by the creation unit 11f, and the data display is performed by the display unit 11g.

When integrating a collection of data, the plant design device 1 extracts data (integration candidate) that is a candidate for integration prior to the integration. In the present embodiment, when a certain integration candidate (first integration candidate) and another integration candidate (second integration candidate) are integrated, either the first integration candidate or the second integration candidate is adopted as the data after integration. It may be decided by the user's selection, or it may be decided automatically by the plant design apparatus 1. For example, integration that is difficult to automate may be performed by the former, and integration that is easy to automate may be performed by the latter. Specifically, when integrating candidates of the same type and type of data, the selection of adopted data may be automated. Further, the newer data (latest value) of the first integration candidate and the second integration candidate may be automatically adopted. If no integration candidate is obtained, the integration candidate is extracted again.

The integrated data is stored as an index in the plant design device 1 (storage unit 13) or in the database 2. With such stored data, it is possible to speed up the re-search of the data and to realize the Imozuru search using the past search results.

FIG. 12 is a diagram for explaining the information model in the second embodiment. FIG. 13 is a table for explaining the information model in the second embodiment.

As described above, the information model is a rule for storing device information in the database 2, and is common among a plurality of databases 2. FIG. 12 shows an example of the classes and properties that make up the information model. Further, FIG. 13 (a) shows an example of class attributes, and FIG. 13 (b) shows an example of property attributes.

As shown in FIGS. 12 and 13 (a), class Cls1 is the highest equipment class and has the attributes of name, manufacturer, and price. On the other hand, the class Cls2 is a pump class and has an attribute of capacity in addition to the attribute inherited from the class Cls1. Class Cls3 is a valve class and inherits class Cls1. Classes Cls4 and Cls5 are inheritance classes of class Cls2 and are assigned to the pumps manufactured by A company and the pumps manufactured by B company, respectively. Details of the properties P11 to P15 of the classes Cls1 to Cls3 are as shown in FIG. 13 (b).

In the present embodiment, a plant model is configured by combining a plurality of information models having such a configuration. Since the plant model is a combination of information models, the contents of the plant model can be recognized by acquiring the data of the information model.

For example, when searching for equipment that meets all the conditions of "manufactured by company A", "output X or more", "installation 10 years or more", "error signal 10 / 1H", "environmental temperature T or more", and "piping connected to A pump". Suppose. In this case, such conditions can be easily set by using the above-mentioned information model or plant model.

FIG. 14 is a flow chart showing an operation example of the plant design device 1 of the second embodiment. FIG. 14 shows an example of a search based on an information model.

First, the product part of the information model is searched using the equipment specified by the user as a key, and the class closest to this equipment is specified (step S11). Next, the product part of the information model is searched starting from the class specified in step S11, and the class to which a wider range of equipment belongs is specified (step S12).

Next, the system part of the information model is searched starting from the class specified in step S12, and the class of the equipment having the related function of the equipment specified by the user is specified (step S13). Next, the location part of the information model is searched starting from the class specified in step S13, and the class of the equipment in the vicinity of the equipment specified by the user is specified (step S14).

Next, a query is generated using the classes specified in steps S11, S12, S13, and S14 as keys, the query is issued to each database 2, and the device instance corresponding to the query is acquired from each database 2 (step S15). ). Next, from the device instances acquired in step S15, only the device instances having a configuration relationship with the class specified in step S11 (hereinafter referred to as “specific class”) are extracted (step S16).

Next, from the device instances extracted in step S16, only the device instances associated with the same loop structure as the specific class are extracted (step S17). Next, from the device instances extracted in step S17, only the device instances that satisfy the constraint conditions regarding the properties of the specific class are extracted (step S18).

Next, if the number of device instances extracted in step S18 is 0, the process returns to step S12 (step S19: YES). On the other hand, if the number of device instances extracted in step S18 is not 0, the process proceeds to step S20 (step S19: NO).

In step S20, the device instances extracted in step S18 are combined to generate a view to be displayed on the display. After that, the above-mentioned specific classes are collectively stored in the information model DB (step S21). The information model DB may be provided in the plant design device 1 or may be any database 2.

FIG. 15 is a schematic view showing the configuration of the plant design system of the second embodiment.

FIG. 15 shows an information model management unit 51 constituting the management unit 11a and an information model DB 52 used by the information model management unit 51. FIG. 15 is further used by the query generation execution unit 61, the query result composition unit 62, and the view generation unit 63 that constitute the acquisition unit 11b, and the query generation execution unit 61, the query result composition unit 62, and the view generation unit 63, respectively. The query pattern DB64, the relationship determination rule DB65, and the filtering rule DB66 are shown. The information model DB 52, the query pattern DB 64, the relationship determination rule DB 65, and the filtering rule DB 66 may be provided in the plant design device 1 or may be any of the databases 2. FIG. 15 further shows specific examples of the databases 2a to 2d and specific examples of the terminal devices 3a and 3b.

The information model management unit 51 is a block that manages information model and plant model data. The information model and the plant model are stored in the information model DB 52.

The query generation execution unit 61 executes the processes of steps S11 to S15. As a result, various classes are specified in steps S11 to S14, and a query is generated and issued in step S15. Further, the device instance corresponding to the query is acquired in step S15. Class identification and query generation are executed using the data in the query pattern DB64.

The query result synthesis unit 62 executes the processes of steps S16 to S19 and the synthesis process of step S20. As a result, various device instances are extracted in steps S16 to S18, and device instances are synthesized in step S19. Extraction and synthesis of device instances are executed using the data in the relationship determination rule DB65.

The view generation unit 63 executes the view generation process of step S20 and the process of step S21. As a result, the view is generated in step S20, and the specific class is stored in the information model DB 52 as a set of data groups in step S21. View generation is executed using the data in the filtering rule DB66.

As described above, in the present embodiment, data is stored and searched based on the information model as shown in FIG. Therefore, according to the present embodiment, it is possible to speed up the search and easily set the search conditions.

Although some embodiments have been described above, these embodiments are presented only as examples and are not intended to limit the scope of the invention. The novel devices, methods, and programs described herein can be implemented in a variety of other forms. In addition, various omissions, substitutions, and changes can be made to the forms of the apparatus, method, and program described in the present specification without departing from the gist of the invention. The appended claims and their equivalent scope are intended to include such forms and variations contained within the scope and gist of the invention.

1: Plant design equipment, 2, 2a, 2b, 2c, 2d, 2e: database,
3, 3a, 3b, 3c: Terminal device, 4: Communication network,
11: Control unit, 11a: Management unit, 11b: Acquisition unit, 11c: Detection unit,
11d: Update part, 11e: Simulation part, 11f: Creation part,
11g: Display unit, 12: Input / output unit, 13: Storage unit, 14: Communication unit,
21: System diagram, 22: Equipment list, 23: Equipment diagram, 24: List of information related to equipment diagram,
25: Single connection, 26: List of information about single connection, 27: List,
31: Engineering screen, 32: Engineering list,
33: Layout map, 34: List of information about layout plan,
41: BOM, 42: List of information about BOM, 43: Setting screen, 44: List,
51: Information model management department, 52: Information model DB,
61: Query generation execution unit, 62: Query result composition unit,
63: View generator, 64: Query pattern DB,
65: Relationship judgment rule DB, 66: Filtering rule DB

Claims (15)

The management department that manages the identification information of the equipment in the power plant,
An acquisition unit that acquires information on equipment in the power plant from the first to Nth (N is an integer of 2 or more) database, and
The information obtained from the K ₁ (K ₁ is an integer from 1 to N) database and the information obtained _{from the K 2} (K ₂ is an integer from 1 to N) database different from the K _{1 database are obtained.} A creation unit that creates display data for displaying information on equipment in the power plant by associating it with the identification information.
With
The management unit includes: the identification information managed by the management unit, and the identification information of the apparatus in said power plant stored in the first K ₁ in the database, stored in the first K ₂ database It manages a list showing the correspondence between the identification information of the equipment in the power plant and the correspondence.
The creation unit, the information from the K ₁ database, whether or not the information from the first K ₂ database is duplicated, it is determined based on the list, on the basis of the said overlap determination result Create display data ,
Plant design equipment. When the creating unit determines that the _{information from the K 1} database and the information from the K ₂ database are duplicated _{, the information from the K 1} database and the information from the K ₂ database are used. The plant design apparatus according to claim 1, wherein the display data is created by using only one of the information of the above. The plant design apparatus according to claim 1 or 2, wherein the creating unit creates a table including information on equipment in the power plant as the display data. The plant design device according to any one of claims 1 to 3, further comprising a display unit that displays the display data on the plant design device or a device different from the plant design device. The creation unit creates the display data for displaying the information obtained by numerical calculation or simulation using the information acquired from the first K ₁ database, to any one of claims 1 4 The plant design equipment described. The display unit secondly identifies the information in _{the K 2 database and the information in the K 3} (K ₃ is an integer from 1 to N) database different from the K ₁ and K _{2 databases.} Display the setting screen for associating with information,
The creation unit associations, is obtained from the first K ₂ database by the identification information being managed and the information obtained the information acquired from the K ₁ database from the first K ₂ database by the management unit information and the information obtained from the first K ₃ database by associating the second identification information, generating the display data,
The plant design apparatus according to claim 4. The acquisition unit acquires the characteristic information from the first to Nth databases that store the characteristic information of the equipment in the power plant in association with the hierarchical structure of the equipment.
Moreover,
A detection unit that detects changes in the characteristic information in the first to Nth databases, and
In the Xth (X is an integer from 1 to N) database, when the predetermined characteristic information of the device having the predetermined identification information is changed, the Yth (Y is an integer from 1 to N) different from the Xth database. In the database, an update unit that updates the predetermined characteristic information of the device having the predetermined identification information, and
The plant design apparatus according to any one of claims 1 to 6. The update unit performs the update so that the updated content of the predetermined characteristic information in the Y database is the same as the changed content of the predetermined characteristic information in the X database. , The plant design apparatus according to claim 7. The Y database to be updated by the update unit stores the predetermined characteristic information of the device having the predetermined identification information among the first to N databases other than the X database. The plant design apparatus according to claim 7 or 8, which is each database. The plant design apparatus according to any one of claims 1 to 9, further comprising a simulation unit that simulates the operation of the power plant using the characteristic information in the first to Nth databases. The first to Nth databases include a plurality of design field-specific databases for designing the power plant for each design field, a CAD database for storing CAD (Computer Aided Design) drawings and list information, and the power plant. The plant design apparatus according to any one of claims 1 to 10, which includes at least one of a specification information database for storing specification information of the equipment in the plant. The creation unit, on the basis of the information of the devices in the power plant to the information model to manage on the basis of the class of the device, integrated with information from the first K ₁ database, and information from the first K ₂ database The plant design apparatus according to any one of claims 1 to 11, wherein the integrated information is stored for re-searching the information of the device. The management department manages the identification information of the equipment in the power plant,
Information on the equipment in the power plant is obtained from the first to Nth (N is an integer of 2 or more) database.
The information obtained from the K ₁ (K ₁ is an integer from 1 to N) database and the information obtained _{from the K 2} (K ₂ is an integer from 1 to N) database different from the K _{1 database are obtained.} By associating with the identification information, display data for displaying the information of the equipment in the power plant is created.
Including that
In addition,
And the identification information managed by the management unit, and the identification information of the apparatus in said power plant stored in the first K ₁ in the database, the power generation within the plant stored in the first K ₂ database The management unit manages a list showing the correspondence between the device identification information and the device.
And information from the first K ₁ database, whether information and is duplicated from the first K ₂ database, determines on the basis of said list, to create the display data on the basis of the overlapping of the determination result ,
Plant design methods including that. The first to Nth databases include a plurality of design field-specific databases for designing the power plant for each design field.
The plant design method according to claim 13, further comprising executing the design of the power plant in parallel for a plurality of design fields using the plurality of design field-specific databases. A plant design program that allows a computer to execute a plant design method.
The method is
The management department manages the identification information of the equipment in the power plant,
Information on the equipment in the power plant is obtained from the first to Nth (N is an integer of 2 or more) database.
The information obtained from the K ₁ (K ₁ is an integer from 1 to N) database and the information obtained _{from the K 2} (K ₂ is an integer from 1 to N) database different from the K _{1 database are obtained.} By associating with the identification information, display data for displaying the information of the equipment in the power plant is created.
Including that
The method further
And the identification information managed by the management unit, and the identification information of the apparatus in said power plant stored in the first K ₁ in the database, the power generation within the plant stored in the first K ₂ database The management unit manages a list showing the correspondence between the device identification information and the device.
And information from the first K ₁ database, whether information and is duplicated from the first K ₂ database, determines on the basis of said list, to create the display data on the basis of the overlapping of the determination result ,
A plant design program that includes that.

Images