JPH0934923A - Building/equipment design supporting method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform the automatic retrieval/correspondence of relating design data, to design buildings and equipments by trials and errors while autonomously verifying the relation of the design data over plural stories without visually confirming a drawing, to automatically extend design change among the drawings, to shorten design time and to prevent design omission. SOLUTION: In a building/equipment design supporting system, by a design knowledge selection part 508 and a design data comparison part 504, the relation of the design data drawn separately for the respective stories is retrieved while referring to design knowledge. Further, by a relating information generation part 507, data for describing the relation of the design data are automatically generated. Also, respective members are discriminated by coordinates so as to eliminate the need of recalculating the entire consistency for the elimination and addition of the data. Further, by a design data change part 505, even when the positional relation and sizes of the members to be combined are different or when added attributes are erroneous, they are autonomously changed based on relating information.

Description

Detailed Description of the Invention

[0001]

The present invention relates to a CAD for construction / equipment design.
The present invention relates to a (computer-aided design apparatus), and more particularly, to a method for autonomously performing design data interlocking change between design drawings input by dividing into a plurality of floors according to design knowledge.

[0002]

2. Description of the Related Art In the past, in architectural design, consistency of design information between systems has been maintained based on an attribute model in which attributes of respective parts are associated and managed in order to handle design data in an integrated manner. This describes each member with a dependency relation between a plug and a socket as shown in "A Consideration on Conceptual Model Description Language for Requirements Analysis", IEICE Technical Report Intelligent Software p1 to p8. For example, a plug is defined on the wall side and a socket is defined on the pillar side to describe the interdependence of columns and walls, and the relationship between members is described in advance by describing the relationship between the plug and socket.

[0003]

However, in the method utilizing such design knowledge, in order to describe the dependency between the building members, the dependency relation between the plug and the socket is described in advance as the building knowledge together with the name of the building member. However, there was a problem that the scope of application was limited.

In a building such as a building having a plurality of floors, pillars, sanitary equipment, air conditioning equipment, electric equipment, etc. are laid over a plurality of floors. On the other hand, CAD (Computer Aided Design) for these buildings and equipment
When designing using equipment, building frames and equipment design drawings are created for each floor. However, building data such as pillars and facility data such as piping are not independent on each floor, so it is necessary to make the floors relevant. By adding relevance to these design data, the related design data can be changed when the design data is changed.

The present invention proposes a method of autonomously making the association information and design modification using this information based on the design knowledge.

[0006]

In order to solve these problems and to be applicable not only to construction but also equipment design, the present invention has a function of managing design knowledge in a construction / equipment design support system. By providing a function to compare design data, the relevance of design data written separately for each floor is searched with reference to design knowledge. Furthermore, by providing a function for describing the relationship between design data as data, data describing the relationship between design data is automatically generated. Here, it is preferable to identify each member by coordinates so that it is not necessary to recalculate the overall consistency even when data is deleted or added. Furthermore, by adding a means to change the position and size of design data, these can be changed autonomously based on related information even if the positional relationship and size of the combined members are different or the added attribute is incorrect. Let

Therefore, it is described as design knowledge that pillars are shared only between designated floors, and in which piping facilities and the like are connected only between floors. Then, by referring to such design knowledge, it becomes possible to retrieve the relationship between the design data. In addition, data that defines relevance is automatically added to the design data, and it is possible to autonomously change the linkage by referring to the data. Linked updating can be performed by once creating and referring to the relationship description data.

[0008]

[Function] In the building / facility design support system, by adding the function of comparing design data to the function of managing design data, the design knowledge is referred to and the relationship between the design data written separately for each floor is confirmed. Search for. Then, by adding a means for defining the relationship between the design data, the data describing the relationship between the design data is automatically generated. Here, each member is represented by a coordinate identifier so that it is not necessary to recalculate the entire consistency for deletion or addition of data, and each member can be searched by coordinates instead of unique numbers. This can save the trouble of resetting the unique number. Linked changes can be made by creating and describing data that describes the relationship. Furthermore, by adding a means to change the position and size of design data, even if the positional relationship and size of the members to be combined are different or the added attribute is incorrect, these are autonomously corrected based on the relevance information. it can.

[0009]

EXAMPLE FIG. 1 shows a specific example of the interlocking change of the frame design and equipment design according to the present invention. 101 to 108 are pillar data, and 109 to 112 are piping data. Pillars and pipes are drawn across multiple floors so that the layout, size, and shape are common. Therefore, the design changes of these graphic data extend to other floors.

1A is a design drawing of the first floor, and FIG. 1B is a design drawing of the second floor. Then, the blueprint of the first floor is used as a reference for layout, size, and shape. It is assumed that the pillars are managed to be common to each floor. At this time, the pillar data 101 and the pillar data 113,
102 and 114, 103 and 115, 104 and 116, 1
05 and 117, 106 and 118, 107 and 119, 10
8 and 120 have the same arrangement, size, and shape. However, in FIG. 1B, the positions of the pillar data 113 and 114 do not match. The size of the pillar data 119 is 1
It does not match 07. Therefore, according to the design drawing of the first floor, which is the reference, as shown in FIG.
The position of 3,114 is changed to 123,124. Further, the size of the pillar data 119 is changed to 125, which is the same size as the pillar data 107. 111 for piping data
, 121, 112 and 122 are made common to the same position and size. On the other hand, the piping data corresponding to 109 and 110 are not entered on the second floor. Therefore, the corresponding piping data is generated in the blueprint of the second floor. These are 126 and 127. In the present invention, the design data is changed autonomously based on such propagation.

FIG. 2 shows the configuration of a system that supports the skeleton design and equipment design. Here, it is composed of a design data management server 201 that manages design data and performs interlocking change by ripple propagation, and individual floor design clients 202 and 203 that perform frame / facility design for each floor. There may be only one individual floor design client. The design data management server 201 receives the design data drawn by the individual floor design clients 202 and 203, and changes the design data by ripple propagation based on the design knowledge designated in advance,
Manage design data consistency. The individual floor design clients 202 and 203 design the frame / facility of each floor. The design data drawn by the individual floor design client is sent to the design data management server. Then, the design data is matched here. The printer 205 outputs the design drawing. The digitizer 206 is used to input design information written on a design drawing into a computer. The input drawing data is sent to the individual floor design client. Here, the design data is modified.

The functional configurations of the design data management server and the individual floor design client are shown in FIG. The individual floor design client 302 is a design control unit 3 that performs design based on graphic input.
03, a design data management unit 304 for managing the designed drawing data. The design drawing data 305 designed by the individual floor design client is sent to the design data management server 301. The design data management server 301 is composed of a design data management unit 306 that manages the consistency of design data and a design knowledge management unit 309 that manages design knowledge that is referred to when changing a figure. The design data management unit 306 controls the design drawing data 3 sent from the individual floor design client.
Manages 07 consistency. When the layout and the size of the design data of each floor are restricted, the relevance description data 308 indicating that the restriction is applied is automatically generated. The design knowledge management unit 309 determines whether to create the relevance description data based on the design knowledge. Regarding design knowledge, system knowledge data is constructed from the system diagram written before the individual floor design for facility design, and building knowledge data is constructed from the building guideline for frame design.

In the building knowledge data, the range showing the commonality of the frame data is described. The system knowledge data describes the specifications of the terminal equipment of the piping and the connection information of the piping. FIG. 7 shows a specific example of the building knowledge data 707 and the system knowledge data 708.
The building knowledge data 707 shows the description of the pillar. Here, the standards for the layout and size of columns are written in the design drawing data of the first basement floor, indicating that the columns are shared from the first basement floor to the tenth floor. The system knowledge data 708 describes the connection of piping. Then, the piping extends from the designated pump (on the first basement floor) to the fifth floor, which indicates that the piping is further connected to the relay pump.

When the design data management server determines that there is a relationship between the design data, the relationship description data as shown in FIG. 4 is automatically generated. The upper drawing number 401 indicates the number of the drawing which is the origin of the update in the related design data. The subordinate drawing number 402 indicates the number of the drawing which is subject to the spillover change. Reference numeral 403 is the coordinates of the reference point (origin) of the upper drawing. It is a coordinate correction amount indicating the difference between the reference point of the lower drawing and the reference point of the upper drawing. This correction amount is used to align the coordinates between the drawings. Reference numeral 406 indicates the identification coordinates of the design data written in the upper drawing. Reference numeral 407 is an identification coordinate of the design data written in the lower drawing. Here, the design data is identified by coordinates. Therefore, it is not necessary to uniquely assign a number (identification number) to the design data. It is assumed that the identification number is adopted to identify the design data of the association description data. When the design data is deleted, the identification number becomes a missing number, so the identification number may be changed again so that it becomes a serial number. In this case, it is necessary to sequentially retrieve all the link designation data and update the identification number. This effort can be saved by using the identification coordinates of the design data. The identification coordinates are set so as to overlap the design data. When the size or rotation of the figure occurs, the coordinates will be reset, but the change of the coordinates is locally limited, and the labor of the processing is small. When such relevance description data is created, the linked change can be performed by referring to the information described in this. Since the relationship description data is created in the process of designing, it is not necessary to define all necessary design data relationships in advance.

A method of interlocking and changing the design data by using such relation description data will be described. Since the interlocking change is performed by the design data management server, attention is paid to the detailed functional configuration of the design data management server, which is shown in FIG. The design data transmission / reception unit 501 has a buffer function of exchanging design data between the design data management server and the individual floor design client. Design data input unit 502
Is a receiver for inputting design data created by the individual floor design client. Design data output unit 50
Reference numeral 3 is a transmitter for transmitting design data of a designated floor in accordance with a request from an individual floor design client.

The design data comparison unit 504 compares the design data of the adjacent floor with the design data of the adjacent floor when sent, and specifies the consistency of the related design data according to the design knowledge. The design data changing unit 505 corrects design data that is inconsistent. This correction means is composed of processes such as moving, resizing, and rotating. The design data input / output unit 506 inputs / outputs design data to / from a storage device (hard disk or the like). The related information generating unit 507 makes an entry of the relationship description data with respect to the newly added design data. This entry is done autonomously within the range specified by the design knowledge. Design knowledge selection section 5
08 selects knowledge data to be used according to whether the knowledge used for design data comparison is construction knowledge or system knowledge. The design knowledge data management unit 509 inputs / outputs knowledge data to / from the storage device.

Next, a procedure for autonomously changing the design data by using the above-mentioned function will be described. The design data interlocking change algorithm is shown in FIG. This algorithm will be described below in combination with FIG.

(1) The design data management server receives the design data created by the individual floor design client (step 601).

The design data is the design data transmission / reception unit 50.
Receive with 1. Then, if the data is sent to the design data input unit 502 and is compressed, it is expanded.

(2) A reference design data is searched on the floors before and after the designed floor (step 602).

When design data is transferred from the design data input unit 502 to the design data comparison unit 504, the design data input / output unit 506 is activated. Then, design DB 510 is searched for design data having consistency on the front and rear floors.

(3) When there is no floor before and after (step 60)
In 3), the received design DB is stored in the design DB as it is (step 604). Then, the server process ends (step 605).

Here, the reference floor of the entire building is the first floor. If the design data of the third floor is sent at this time, it is once stored in the design DB. Then, when the design data of the second floor is sent, the interlocking change is performed between the first floor and the second floor. Then, subsequently, interlocking change is performed between the design data on the second floor and the design data on the third floor.

(4) The corresponding relevance description data is retrieved (step 607).

This is performed for each design data that may be connected (step 606). Then, it is searched whether the relevance description data has been created for the newly added design data or has not been constructed yet.

(5) If there is no relevance description data (step 608), the corresponding design knowledge is searched. If the selected figure is pillar data, the building knowledge is searched, and if it is piping data, the system knowledge data is searched.

(6) Relevant design data are retrieved according to the design knowledge (step 608).

First, the design data of related floors that are consistent with each other are retrieved. This corresponds to searching for a figure on the identification coordinate of the association description data. The design data having the identification coordinates is searched, and the design data included in the design data as the circumscribed quadrangle (the floor of which the consistency is desired) is searched. In FIG. 7, pillar data 701 and piping data 70
The layout and size of 2 are the criteria for interlocking changes. Pillar data 7
For 01, the pillar data 703 is searched. As in the case of the piping data 702, the piping data 705 is selected. The design data comparison unit 504 searches for the related design data. Then, it is determined whether or not the design data is related design data based on the design knowledge data obtained by the design knowledge selecting unit 508.

(7) Relevance description data is created (step 610).

The structure of the relationship description data is shown in FIG. Here, as the identification coordinates 407, the coordinates of the newly added design data are stored. The identification coordinates are set on the characteristic points and the points on the line that make up the graphic data. If this point overlaps another figure, the identification coordinates are changed. This change may be part of the relevance description data. In fact, when changing the identification of one piece of design data, it is only necessary to retrieve and change a maximum of two pieces of relevance description data. The relevance description data is stored in the relevance description data table.

(8) The design data is interlocked and changed.

A figure whose size and position of the related data are different is changed (step 61).
1).

(9) Save design data and connection designation data (step 612).

The design data input / output unit 506 saves the design data and the link designation data.

The flow in the case of designing a building / equipment using the above algorithm will be described with reference to FIG.

System knowledge data and architectural knowledge data are used as design knowledge. As mentioned earlier, the building knowledge data shows that the pillars are continuous from the first basement floor to the tenth floor. If the pillar is implicitly understood, it can be easily generated automatically. Building knowledge data 70
Since 7 is designated only as a pillar, the processing is common to all pillars. The system knowledge data can be obtained by tracing the relationship between the terminal equipment written on the system diagram and the connecting parts such as piping and electric wires. The system knowledge data 708 shows the tap water pipes, and the pumps installed on the first basement floor are connected by pipes from the first basement floor to the fifth floor, and the booster pump is further provided on the fifth floor. Show.

The standard floor is the first basement floor. Therefore, the design drawings on the first basement floor will be the standard for interlocking changes. When the design drawing of the ground floor is sent, the relationship between the design data is searched. The pillar data is searched from the design data on the first basement floor. As a result, the pillar data 701 is searched. This is selected from the building knowledge data 707 because the pillar data is subject to restrictions on the arrangement and size. Next, the pillar data 703 from the design data on the first floor is used as a candidate for the interlocking change.
It is searched based on the arrangement coordinate of 1. Pillar data 701
Since the arrangement coordinates of 703 are different, the pillar data 703 is moved to the position of 704. The relevance description data 709 is automatically created by changing the arrangement of the pillar data. As the identification coordinates of the pillar data, the representative coordinates (x
1, y1) is stored. The walls and pillar reference lines on the same floor will also be changed by the interlocking change means prepared for each floor.

Next, the piping data 705 becomes a candidate for interlocking change. This can be understood from the fact that the system knowledge data 708 imposes restrictions on the arrangement and size. First, the piping data is underground 1
Search from the floor design data. As a result, the piping data 702 is retrieved. Next, the piping data 705 from the design data on the ground floor is used as a candidate for the interlocking change.
2 is searched based on the arrangement coordinates. Piping data 70
2 and 705 have different arrangement coordinates, the piping data 705 is changed to the position 706. The relevance description data 711 is automatically created by changing the arrangement of the piping data.
Representative coordinates (x2, y2) after the piping data is changed are stored as the identification coordinates of the piping data.

[Multiple-story building /
Consistency of design data such as equipment is maintained. The design data changed by the design data management server sends the drawing data according to the request of the individual floor design client.

[0040]

According to the design support method of the present invention, it is possible to automatically search / associate related design data by referring to the design knowledge, and it is possible to extend over a plurality of floors without checking the drawings. It is possible to design buildings and facilities by trial and error while autonomously verifying the relationship between design data. Furthermore, since automatic correspondence can automatically propagate design changes between drawings, design time can be shortened and design omission can be prevented.

[Brief description of drawings]

FIG. 1 is an explanatory diagram showing a linked correction of design data over a plurality of drawings.

FIG. 2 is an explanatory diagram showing a device configuration of a design support system.

FIG. 3 is a block diagram showing a functional configuration of a design support system.

FIG. 4 is an explanatory view showing the structure of a design element relation data table.

FIG. 5 is a block diagram showing a functional configuration for performing linked update.

FIG. 6 is a flowchart showing a design data linkage change algorithm.

FIG. 7 is an explanatory diagram showing a specific example of interlocking change.

[Explanation of symbols]

501 ... Design data transmitting / receiving unit, 502 ... Design data input unit, 503 ... Design data output unit, 504 ... Design data comparing unit, 505 ... Design data changing unit, 506 ... Design data managing unit, 507 ... Related information generating unit , 508 ... Design knowledge selection unit, 509 ... Knowledge data management unit, 510 ... Design D
B, 511 ... Knowledge DB.

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Toichiro Takita 1 Horiyamashita, Hadano City, Kanagawa Prefecture, Hitachi Computer Engineering Co., Ltd. Central Research Laboratory

Claims (4)

[Claims] 1. In a computer-aided architecture / facility design system having graphic drawing means, when there is a relationship such as a layout of design data between design drawings input by dividing into a plurality of floors,
Search related design data by referring to building / equipment design knowledge obtained from system diagrams, etc., and automatically generate and refer to related information indicating the relationship of design data when there are restrictions on layout and size. A method for supporting building / equipment design, characterized in that design data interlocking changes are made between design drawings input by dividing into multiple floors. 2. A design data input means for receiving design data, which is means for managing the design data, a design data output means for outputting the design data, and a design data input / output means for managing the storage of the design data. The architecture / equipment design support system compares the design data with the design data of the related floor and retrieves the related design data according to the design knowledge, the design data comparison means, the design data change means for interlocking the design data, the design data It has a related information generating means for registering and further referring to the relation, a design knowledge selecting means for retrieving design knowledge data, and a design knowledge data input / output means for storing and managing knowledge data, and sends design drawing data through the design input means. Then, by referring to the design knowledge data retrieved by the design knowledge data input / output means and the design knowledge selection means, When changing the layout or shape of the design data, the related information generating means generates the relationship of the related design data as data, and the design data changing means automatically performs the layout change and the shape change between the design data. A building / equipment design support method characterized by autonomously matching unmatched parts. 3. The architecture according to claim 1 or 2, wherein the design data reference identifier required for associating the design data is determined by the representative coordinates of the figure, and the figure is searched to identify the figure by the coordinate. / Equipment design support method. 4. A step of receiving design data created by a client by a design data management server, a step of retrieving reference design data on floors before and after a designed floor, and when there is no floor before and after. The step of storing the received design data in the design database as it is, and searching for the relevance description data corresponding to the above data,
The step of searching whether the relevance description data has been created or not yet constructed for the newly added design data and the corresponding design knowledge when there is no relevance description data are searched and selected. If the figure is pillar data, there is a step of searching for building knowledge, and if it is piping data, searching for systematic knowledge data, and a step of searching for related design data according to design knowledge and creating relationship description data. Building / equipment design support method.