JPH11120221A - System for sharing object model and recording medium storing program used for realizing the system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To share an object model between operation support programs different in a description form. SOLUTION: A building model (object model) 15 described in one form is provided. An output I/Fs 11 and 13 for delivering data on the building model 15 to plural applications (operation support program) 21 and 22 and an input I/Fs 12 and 14 for putting the processing result data of the plural applications back to the building model 15 are provided. Those output and input I/Fs 11 to 14 exchange the data and also convert the description form at need.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a plurality of existing (or future-created) business support programs (applications / applications) relating to a plurality of processes in at least a part of a series of processes from design of an object to manufacturing through management. The present invention relates to a system for sharing data representing a model of an object between programs, and a recording medium (program tool) storing a program used to construct the system.

Here, the object includes various products, buildings, bridges, ships, plants and the like. Therefore, manufacturing is a concept that includes not only manufacturing in the most general sense (for example, of a product) but also construction, construction, assembly, and the like.

[0003]

BACKGROUND OF THE INVENTION Objects in the above sense are generally manufactured through a series of multiple steps. Although it depends on the type of object, the general flow is: basic plan; evaluation, detailed design; estimation; estimation; procurement, manufacturing, and maintenance. Various business support software (computer programs), so-called application software, are used in each of these steps. The main types of business support software used in the above processes are: basic design; various (design,
It is software for detailed design, structure (equipment, strength, flow rate) calculation; quantity calculation; cost calculation; drawing creation, production planning, production management; repair planning, budget management, etc.

In most of these business support software, data on an object (the structure, shape, dimensions of the object, types of various elements constituting the object, its shape, dimensions, material, unit price, arrangement, various types of equipment, etc.) (A set of data representing types, arrangements, etc.) is input or created. Generally, data representing an object becomes richer and more detailed (grows) as it goes through the process. If a change (design change, etc.) occurs in a previous step, data relating to the object is changed accordingly, so that it may be necessary to repeat the processing in the subsequent step. Conversely, depending on the processing result in the subsequent process, it is necessary to change the data on the object determined in the previous process.

Conventionally, the above-mentioned various business support software is often developed and created by software houses in fields in which they are good at. In one process, a plurality of business support software developed by different software houses may be used. Since each business support software is developed by a separate software house, generally, the description format of data representing an object is often different. This is due to the fact that the business support software has a specific data format suitable for its application processing. For this reason, electronic data representing an object cannot be used mutually between different business support software, and a document (document, drawing, etc.) is once created from the object data in one business support software, and this document is created. It is necessary to input target object data for other business support software while referring to. This re-entry operation itself not only wastes time and effort, but also causes problems such as inability to maintain quality due to input errors and failure to input change information. This was an obstacle to shortening the process.

[0006] In order to solve this problem, an approach has been made to create an interface for exchanging data between different business support software. However,
Since the interface must be created individually for almost all combinations of many business support software,
As the number of interfaces becomes enormous and one business support software is revised, the interface between the business support software and all other business support software that needs to exchange data must be revised. .
This is almost impossible.

[0007]

DISCLOSURE OF THE INVENTION The present invention provides a system capable of sharing data (object model) representing an object among a plurality of business support programs.

Another object of the present invention is to provide a system capable of sharing an object model among a plurality of business support programs having different description formats for data representing an object.

The present invention further shares an object model among a plurality of business support programs, and updates each business support program with the latest object model data that grows or changes in accordance with processing by each business support program. It provides a system where programs can be used and can be added, updated or changed as needed.

Further, the present invention provides a core tool for constructing a sharing system of an object model, that is, a recording medium storing a program used for constructing the sharing system.

The present invention is a plurality of business support programs for at least a part of a plurality of processes in a process from design of an object to manufacturing through management, at least two of which are descriptions of an object model. This system provides a system for sharing the object model among such multiple business support programs in a different format, each business support program is responsible for one or more processes or a part of the process. The system includes a database management system including a database for describing the object model in one format for a plurality of business support programs and storing data representing the object model, and a business support program. Is provided between the database management system and the database management system. An output interface that is obtained from the database through the management system and is converted into a description format compatible with the business support program, and is provided between the business support program and the database management system and generated by the business support program. And an input interface for converting the data into a description format of the object model and writing the data in a corresponding location of the database through the database management system.

The object model includes data representing the structure, shape, and dimensions of the object, the types of elements constituting the object, their shapes, their dimensions, their positional relationships, unit prices, materials, and the like. Is defined according to

According to the present invention, an object model described in one format shared by a plurality of business support programs is prepared. Even if the description format of the data in the object model is different from the description format of the business support program, the description format is converted at the output interface and the input interface, so a pair of output and input interfaces are prepared for each business support program. By doing so, all business support programs can use the object model.

Therefore, it is not necessary to input object data for each business support program, so that labor and time for the work can be saved, and problems due to input operation errors and the like can be solved. Further, even if the business support program is revised, only the pair of output and input interfaces corresponding to the business support program need to be revised, so that it is easy to cope.

According to the present invention, since a plurality of business support programs can share one object model, changes, corrections, and the like made to the object model data by the business support program in the previous process can be performed by the business support program in the subsequent process. Is reflected in the application processing of. Even if the data determined by the work support program in the previous process is changed or modified by application processing of the work support program in the subsequent process, the result is always reflected in the object model.

In a preferred embodiment of the present invention, the database management system is an object database management system. In this case, a part of the utility program included in the object database management system is incorporated in the input / output interface. Utilities can be shared by many programs.

In another embodiment of the present invention, means for inputting data representing the object model to the database, means for modifying data representing the object model in the database, and Means is provided for outputting and displaying data representing the object model of the base.

This system can input object model data as it is without the help of a business support program,
Correction and output are possible.

There are various modes for sharing the object model. In the above-described system, the object model data is provided from the database to the business support program via the output interface, and the data generated (including changes, corrections, etc.) by the business support program is transmitted through the input interface. Written on the base. The object model data moves bidirectionally between the database and the business support program.

There is also a form in which the object model data moves in one direction. That is, the object model data is output from the database to the business support program through the output interface, and is used in the business support program.

The present invention also provides a system for sharing an object model among a plurality of business support programs in the latter form. The system includes a database management system including a database for describing the object model in one format for a plurality of business support programs and storing data representing the object model. A means for separately inputting data representing the object model into the database through the database management system, and a means provided between the business support program and the database management system; An output interface for acquiring necessary data from the database through the database management system and outputting the acquired data to the business support program.

This system is used, for example, as follows. Through the above-mentioned input means, data representing a trial (hypothetical or provisional) object model is obtained from a data source.
Entered in the base. The object model data of this attempt is provided to the business support program through the output interface. Using the business support program, the object model of the trial is verified whether it is appropriate or not (for example, by outputting (displaying) the object model on the business support program side). A plurality of business support programs can verify one common object model from a different viewpoint. The object model is changed or modified or new data is added to the object model according to the verification result of one business support program, and the updated object model is used in the same business support program or in another business support program. It can be re-verified by a support program.

When the data description format of the object model and the data description format of the business support program are the same, the data conversion process is not necessary, so the data output process is not limited as a function of the output interface. In this case, the output interface only needs to simply transfer data. Of course, when the data description format is different between the object model and the business support program, an output interface that converts the object model data into a description format compatible with the business support program is used.

An input interface, provided between the business support program and the database management system, for writing data generated by the business support program to a corresponding location of the database through the database management system. It goes without saying that the provision of such an arrangement allows data to be moved bidirectionally between the database and the business support program.

As described above, when the description format of data in the object model and the description format of data in the business support program are the same, the interface does not need to perform data conversion processing. Replacement) may be provided.

The object model sharing method and system according to the present invention, assuming that data conversion is not necessarily required, are defined as follows.

That is, in the object model sharing method according to the present invention, an object model described in a single format for sharing the object model among a plurality of business support programs is stored in the business support program. Is provided independently, data is input to the object model separately from the business support program, and data is exchanged between the business support program and the object model via an interface.

An object model sharing system according to the present invention is provided independently of the above-mentioned business support program for storing an object model described in one format and shared by a plurality of business support programs. And a means for inputting data to the object model separately from the business support program, and an interface for exchanging data between the business support program and the object model. Things.

The present invention provides a program recording medium serving as a tool for constructing the object model sharing system described above.

A recording medium according to the present invention is a database provided independently of the business support program for forming an object model described in one format shared by a plurality of business support programs. A program for inputting data into the database separately from the business support program, and exchanging data between the business support program and the database (moving data in one direction only) The utility program for creating the interface is stored.

The database framework in one embodiment is a database management system. An object database management system can be used as the database management system. In this case, a utility program used in the object database management system is included in the framework of the database. If a database management system or an object database management system that has already been created (commercially available) is used, the database framework described above is read into these database management systems, It will be a definition (class) that specializes the database management system for a particular application.

A user loads this recording medium into a computer and creates an output interface (or at least one of them) for a desired business support program using a utility program stored therein. be able to. In addition, if the object data is input directly from the business support program using the input program or through the created interface, the object model is created according to the database framework. The user can drive the business support program using the object model including the basic data, use the data of the object model, and enrich the contents of the data.

[0033]

DESCRIPTION OF THE PREFERRED EMBODIMENTS A system in which a plurality of application programs for supporting a building operation share a building model (object model) will be described.

Existing application programs for supporting building operations include programs for supporting planning, design design, structural design, equipment design, estimation, construction, maintenance, sales, and the like. Each of these programs
It has a data description format suitable for the application processing (processing executed by the application program).

FIG. 1 shows an outline of the configuration of a system for sharing a building model among a plurality of existing application programs. FIG. 2 shows a program configuration of a building information modeler constituting this system in a partially overlapped form with FIG.

The building model sharing system includes a building information modeler 10. The building information modeler 10 includes a building model (object model) 15, a model editor 16, a model viewer 17, and a utility 18. Architectural Information Modeler 10
Includes a plurality of output interfaces (output I / F) and input interfaces (input I / F). The output I / F and the input I / F form a pair. Here, two pairs of output and input I / Fs are shown for convenience. That is, a pair of the output I / F11 and the input I / F12, and the output I / F13 and the input I / F14.
Is a pair with.

The building model sharing system further includes a plurality of application systems. Here 2
Two application systems 21 and 22 are shown corresponding to the pair output and input I / F.

The building information modeler 10 is actually a computer system (input / output devices such as a keyboard, a mouse, a display unit, and a printer, and a CD-ROM drive, a hard disk drive, etc.) on which a program is mounted. (Including a storage device). The building model 15 is a data base system built in this computer system. The model editor 16, the model viewer 17, the utility 18, and the entities of the output and input I / Fs 11 to 14 are provided by the computer
This is a program installed in the system.

The application systems 21 and 22 are also realized by a computer system on which application programs are installed.

The building information modeler 10 and the application systems 21 and 22 can be realized by separate computer systems. In this case, the plurality of computer systems are communicably connected to each other (or exchange data). The building information modeler 10 and the application systems 21 and 22 can be realized by one computer system. In this case, the building model (data base), model editor 16, model viewer 17, utility 18, output, input I / F program, and application program are stored in one computer system.
In the following description, the application systems 21 and 22 are simply abbreviated as applications 21 and 22.

When the applications 21 and 22 are used alone (that is, not used in this building model sharing system), the applications 21 and 22 receive input data on a building in a predetermined description format and receive the input data. Store in database. In response to the provided input data, processing conditions, and commands, the application performs the specified application processing. The application processing result is stored in a database or output (displayed or printed) as required. The application processing result also has a description format specific to the application. Generally, the description formats are different between the applications 21 and 22 (although the same may occur naturally), there are many cases where the data regarding the buildings is not compatible.

In the building model sharing system, data relating to buildings required for application processing in the applications 21 and 22 and other applications is described in one format to form a building model 15. The structure of the database that makes up the building model will be described later,
The building model consists of site shape, building outline, number of floors, room allocation, floor height, roof shape, pillar arrangement, dimensions and materials, wall arrangement,
A collection of data related to buildings, such as their dimensions and materials, beam arrangements, their dimensions and materials, elevating equipment arrangements, air conditioning and sanitary equipment arrangements and model numbers, electrical equipment arrangements and model numbers, and these data are hierarchically linked to each other. , And settings,
It can be changed and taken out.

In the building information modeler 10, the model editor 16 performs processing relating to the input of building model data, processing for associating the input data with each other as necessary, and storing the data in the database of the building model 15; Processing such as modifying base model data is performed. model·
The viewer 17 performs a process of displaying the input model data in the course of the input process, a process of extracting the model data from the database and displaying the model data in a three-dimensional perspective view. The user can operate the model editor 16 and the model viewer 17 to input or display the building model data in the building information modeler 10 and check it. A specific example will be described later.

The input and output I / Fs 11 to 14 are interfaces between the building model 15 and the applications 21 and 22. That is, the output I / F 11 extracts data on the building required by the application 21 from the building model 15,
This is converted into a data description format suitable for processing in the application 21 as necessary, and is passed to the application 21. Application 21 receives the data
The specified application processing is performed according to the input processing conditions. The data obtained as a result of the processing is converted to the description format of the building model 15 by the input I / F 12 as necessary,
It is returned to the building model 15 and output from the application 21 as needed. Similarly, the output I / F 13 extracts data on the building requested by the application 22 from the building model 15, converts the data into a data description format suitable for the processing in the application 22 as necessary, and transfers the converted data to the application 22. The application 22 performs a predetermined (commanded by input) applied processing on the received data according to the input processing conditions. The data processed by the application processing is converted into the description format of the building model 15 by the input I / F 14 as necessary, and is returned to the building model 15. It is output from the application 22 as needed.

The utility 18 is a model editor 16,
This is a group of (program) routines commonly used by the model viewer 17 and the input / output I / Fs 11 to 14. The main functions include setting of member information, acquisition of member information, drawing,
There are geometric shapes, menu controls, etc. The setting of the member information is for writing (set) the given model data to the database of the building model 15, and the acquisition of the member information is to read the requested model data from the database ( get). The member information acquisition utility is also called a dictionary function. The geometric shape is for defining geometric shapes such as lines, triangles, squares, etc. The drawing is for drawing the shape on the screen based on the geometric information of the members, the menu control is a menu that can be selected by the user It is for displaying and taking in the result selected by the user.

Although only two applications are shown in FIG. 1, the same applies when there are three or more applications. Output I / according to application
F and an input I / F are provided, and even if the data description format differs between the application and the building information modeler 10 depending on the output and input I / F, data exchange between the application and the building information modeler Is achieved. If the data description format between the application and the building information modeler 10 is the same, the conversion of the data description format is not necessary, so the output and input I / F send and receive the data between the application and the building information modeler 10. Will do.

The data on the buildings included in the building model 15 grows, enriches and becomes more detailed as application processing is performed by various applications. Among the building data input to the building model 15 in the building information modeler 10, there may be data stored in the building model 15 without being processed by any application. Some of the data in the building model 15 may be processed or modified by one application 21. There may also be data on buildings newly created by the application 21 and stored in the building model 15. A part of the data in the building model 15 processed, changed, or created by the application 21 may be passed to another application 22 and modified. The data modified by the application 22 is stored again in the building model 15. The data modified by the application 22 may be passed from the building model 15 to the one application 21 and processed again.

In this way, even if the data relating to the building is changed by the application in charge of the preceding process, the changed data is stored in the building model 15 and the other application which is in charge of the subsequent process as it is. Can be a target of processing. Further, even if the data determined by the application in the previous process is changed as a result of the processing by the application in the subsequent process, the changed data becomes a part of the building model 15. The data in the building model 15 can be processed by all applications. That is, each application has a unique building model, including data processed by other applications.
Any data in 15 can be processed. There is no need to input building model data for each application. Further, since much information including the change information can be incorporated as a part of the building model, it is possible to prevent the operator from overlooking it. These lead to shortening of the construction process.

One of the major features of the building model data sharing system shown in FIG. 1 is that existing application software can be used as it is, and a model can be used among a plurality of existing application software.・ No need to re-enter data
The point is that data can be exchanged arbitrarily. Another feature is that data changed, modified or created by one application software can be used as it is in another application software.

The above-described usage of the building model / data sharing system makes the most of the features of the sharing system. Various types of data move bidirectionally between the building model and the application. This sharing system can also be used in the following forms. Model data is input to the building information modeler using a model editor or a model viewer, and stored in a building model. The model data is passed to the application through the output I / F. The application considers whether the building model is valid or not. The model data is modified using the model editor in the building information modeler so as to reflect the result of this examination. This method is used when creating a more desirable building model by trial and error.

FIG. 3 shows a part of an example of the building model 15. In this embodiment, the building model 15 is an object that stores data on a building in the form of an object integrated with an operation method (procedure) for the data.
It is realized by a database management system. Of course, not limited to the object database management system, other database management systems can be used. In short, it is only necessary to be able to input and output (including change, add, delete, and search) data to and from the database.

For each object such as site, building, floor (floor) (floor list and floor information), member list per floor, column list per floor, etc., attribute information (attribute data) (for example, in the case of site, Address data, data representing the shape of land, etc.). The arrows between the blocks representing the objects represent the connection of the objects (a pointer to the next object).
The column list (floor unit) is linked with detailed data on columns included in the list. The same applies to wall lists (floor units), beam lists (floor units), and the like. For a wall, a list of openings formed in the wall is connected, and each opening is connected to a door or a window (a member of a window) provided therein.

Such a building model 15 is created for each building. Most commonly, the model of Architectural Information Modeler 10
Data relating to the basic structure or shape of the building is input using the input and editing functions of the editor 16 and the model viewer 17 and stored in the building model 15. Instead of this, an initial form of the building model 15 may be created by inputting data regarding a building while performing a basic design using a standard pattern using an application regarding a design design described later. Both the input and editing functions of the building information modeler 10 and the design application can be used together. In any case, this depends on the usage of the sharing system as described above. After that, the data of the building model 15 is enriched, modified, or changed by application processing using a design design, a structural design, or another application.

FIG. 4 shows a procedure of processing for inputting model data of a building model in the building information modeler.
This process is performed by Model Editor 16 and Model Viewer.
This is processing according to 17 (this is basically processing of the model editor, but processing by the model viewer is also involved in connection with display).

When the architectural information modeler is started, first, an initial menu screen is displayed. This menu screen is used to select one of three-dimensional perspective view display, member list display, scale change, input, and the like. When the user selects the input, the process proceeds to the process shown in FIG. Needless to say, it is possible to return to the menu screen at any stage of the processing in FIG.

One of the existing projects is selected, or when a new project is created, the name of the project is input (step 51). Site information such as latitude, longitude, address, use area, and site shape is input (step 52). The number of building streets and their intervals (span intervals) are entered (step 53). The number of floors of the building whose model data is to be input is input (step 54).

When the input of the necessary information is completed, a model input / edit screen as shown in FIG. 7 is displayed (step 55). Vertical and horizontal lines (X1 to X4,
Y1 to Y3) are the passing axes. This screen shows the street axes of the designated floor in the form of a plan view based on the number of street axes input and their intervals.

The user moves the cursor to a desired position on the model input / edit screen and clicks the mouse to input information on columns, walls, beams, floors, ceilings, openings, and the like. become. When the intersection of the street axes is indicated, it is recognized as an input of a column, wall, beam, floor, ceiling, etc., and when the wall is indicated by a cursor, it is recognized as an input of an opening formed in the wall (step 56). .

There are three modes for indicating the intersection of the street axes (step 57). The first is to indicate only one intersection. This means setting up a pillar at that intersection. The second is to designate a section by designating two or more intersections. This means forming columns, walls and beams in that section. The third is to designate three or more intersections and designate a region surrounded by the designated intersections. This means forming columns, walls, beams, floors and ceilings in that area.

The instruction of the intersection by the cursor and the end of the instruction of the intersection can be distinguished by the left and right click buttons of the mouse. For example, if there is a right click after one left click, it is a one-point instruction. If an instruction by left-clicking is given twice or more consecutively, a section or an area is designated.

In the case of one-point designation, the position of the designated intersection (represented by the axes X and Y) is read, and this position and the attribute information (size, etc.) (standard value) of the column are defined as the building model. The data is written into the 15 data bases (see the data of the column C1 in FIG. 3), and the columns are displayed on the screen (step 58).

In the case of the section designation, the positions of the designated intersections are read, and link information between the column at that position (if not present, generated at this time), the wall and the beam is created. These pieces of information are written in a data base together with attribute information (wall thickness, etc.) (standard values) of the wall (or beam) (see the data of the wall Wall1 in FIG. 3), and the wall is displayed at the designated position. (Step 59).

Similarly, in the case of area designation, the positions of a plurality of intersections instructed to surround the area are read, and the columns, walls, and beams at that position are generated, and link information is created. These information and attribute information of floor and ceiling (standard value)
Is written to the database and displayed (step 60).

When a wall is pointed by the cursor, the information on the wall is read, and the attribute information (shape, offset, etc.) of the opening and the link information of the wall are written in the data base (see Open1 in FIG. 3). ), And the opening is displayed on the screen (step 61). FIG. 9 shows an example of a screen for inputting attribute information on an opening. Regarding the aperture, the user inputs attribute information according to the format shown in FIG.

The names of pillars, walls, openings, etc. are also entered with the cursor instruction or at an appropriate time later, and are written in the database.

FIG. 8 shows an example of a plan view displayed on the display device when several columns, walls, openings and the like are set. The user can correct the attribute information on the columns, walls, and the like according to the input screen shown in FIG.

The details of the column generation processing in step 58 and the wall generation processing in step 59 are shown in FIGS. 5 and 6 together with a program.

In FIG. 5, "designation of pillar arrangement position"
It instructs a program called drawing View to acquire information indicating the position of the intersection of the axes as instructed on the display screen. "Create pillar" indicates that pillar data should be written to the database. “Display of pillar” indicates that pillar shape information is acquired as line segment information on the plan view and displayed.

In FIG. 6, "generation of wall" indicates that the data of the wall is written in the data base together with the connection information with the pillar.

FIG. 10 shows a system configuration in which a design design application 21A and a structural analysis application 22A are provided in the building information modeler 10 as examples of applications. Outputs and input I / Fs with the design application 21A are a design output I / F 11A and a design input I / F 12A. Output / input I / with structural analysis application 22A
F is a structure output I / F 13A and a structure input I / F 14A.

FIG. 11 shows a design output / input I / F 11 A, 12 B between the design design application 21 A and the building information modeler 10.
3A shows an outline of a processing procedure for exchanging building model data related to a design design.

The design design application 21A is used for basic design, detailed design, design drawing creation, shading, sound, lighting,
It mainly supports design work related to the outline and appearance of buildings, such as airflow calculations. When the application 21A starts,
Prior to the individual application processing or during the individual application processing, various processing conditions (drawing specifications, lighting calculation conditions, etc.) are input by the user (step 101), and commands for specifying individual processing are input. . In the database of the design design application 21A, data relating to the design design already input by the user in the application 21A as the processing proceeds (all or most of this data is also stored in the building model 15) ,
Alternatively, data on the design obtained from the building model 15 is often stored or already stored.

In a certain design design process of the design design application 21A, data relating to a design design required for the process (data not in the data base of the application 21A or missing; data that already exists in the data base may be used. ). Design output I / F
11A extracts the necessary data (layout, dimensions, room space data, etc.) from the building model 15 (step 111),
If necessary, an input data generation process including a process of converting into a description format usable by the design design application 21A is performed (step 112) (the design design application 21A).
If the data description format in the building information modeler 10 is the same as that in the building information modeler 10, no data conversion is required. The input data generation process only needs to place data in a file that can be obtained by the application 21A. This is the same in step 122 described later. ), Design application 21A
(Generally through a file). The design application 21A performs predetermined application processing using the data passed from the design output I / F 11A (step 102).

For example, the design design application 21A
Calculates the lighting through the opening Open1 (or window Wnd1) in the wall Wall1 (see FIG. 3). It is assumed that the design design application 21A needs data on the opening Open1 (and other necessary model data) as building model information. Design output I / F
11A is the object opening Open1 in the building model 15.
(And other objects, if necessary) and retrieve attribute data for that object.

In FIG. 13, a wall Wall1 is located between columns C1 and C2, and an opening Open1 is formed in the wall Wall1. X1 and Y1 are names of axes passing through the center of the column C1. As can be seen from FIG.
, Its shape is rectangular, its size (horizontal length wx1, vertical length wy1),
Offset indicating the position of the opening in wall Wall1 (wall Wa
The horizontal distance x1 and the height h1) from the lower left corner of ll1 to the lower left corner of the opening Open1, and the opening W1 has a window Wnd1.
Is stored. These data are passed from the design output I / F 11A to the design design application 21A.

The design design application 21A uses the data passed from the design output I / F 11A and, if necessary, the data stored in its database or generates necessary data (for example, for the wall Wall1). Information is also obtained from the building model 15, and the height of the opening Open1 from the ground is calculated, for example), and the value of lighting through the opening Open1 is calculated. The required aperture size is calculated by processing such as comparing the calculation result with a necessary or desirable lighting value. It is assumed that the required opening dimensions calculated by the design application 21A are wx2 and wy2 as shown in FIG. 14, and the offsets are x2 and h2.

The new data relating to the opening Open1 is passed from the design application 21A to the design input I / F 12A. The design input I / F 12A stores the new data in the building model 15 in association with the object as new attribute data of the opening Open1 in the building model 15. Thus, in the building model 15, the attribute data of the object opening Open1 is updated (changed).

In other words, in general terms, when the design application 21A performs a predetermined application process related to the design design, the result is passed to the design input I / F 12A (step 121), and the output is provided as necessary. Output to the device (display on the display device) (step 103).
The design input I / F 12A performs processing such as converting the data passed from the application 21A into the description format of the building model 15 as necessary (step 122), and writes the data as attribute data of the object corresponding to the building model 15. Put in. Design output I / F11A is a design design application 21
If the data passed to A is different from the data passed to the design input I / F 12A by the design design application 21A, the data of the building model 15 has been updated (or changed or modified), and In this case, there is no change in the data in the building model 15. The design input I / F 12A may check whether or not the data has been changed, and write only the changed data to the building model 15.
The design input I / F 12A does not need to write the data to the building model 15 if there is no change in the data.

When basic data is set in the building model 15 at the initial stage of building the building information modeler 10, the design design application 21A may be used as described above. Using the input function and the editing function of the design application 21A, data representing a standard pattern or data relating to the basic structure and shape is input in the application 21A. These data are stored in the building model 15 by the design input I / F 12A. In the process of inputting such basic design data, the lighting calculation described above will not be performed. Lighting calculation and aperture design change will be positioned as one of the items to be rechecked at the subsequent detailed design stage.

FIG. 12 shows a structure output / input I / F 13A, 14 between the structure analysis application 22A and the building information modeler 10.
3A shows an outline of a processing procedure for exchanging building model data related to structural analysis (structural design) through A.

The structural analysis application 22A supports operations related to structural analysis including building strength calculation, vibration analysis, etc., and creation of structural drawings. In this application 22A, data relating to the structural analysis input from the application 22A or acquired from the building model 15 is stored in its database or in the initial stage or as the application processing proceeds, or is already stored. May have been.

The structure output I / F 13A transfers data necessary for a certain structure analysis process of the structure analysis application 22A to the structure analysis application 22A. That is, the structure output I
/ F13A converts building model data (such as frame information; arrangement of columns and beams, cross-sectional data of columns and walls, opening data, etc.) related to structural analysis (design) required by the structural analysis application 22A into building models. 15 (step 141), and if necessary, convert it to a description format that can be used by the structural analysis application 22A (step 14).
2), hand over to structural analysis application 22A. Using the received data, the structural analysis application 22A executes predetermined structural analysis (design) application processing in accordance with given processing conditions (setting of external force, etc.) and commands (steps 131 and 132).

The design design application 21 described above
A description will be given of an example of calculating the strength of the wall Wall1 using model data including the opening data changed by A.

The structural output I / F 13A searches the building model 15 for the object wall Wall1 and extracts its attribute data. As for the wall Wall1, the positions are columns C1 and C2.
, And that the cross-sectional data is in Sec1 is stored in addition to the fact that the data is in the middle and the wall thickness is d1. The structure output I / F 13A searches for the object Sec1, and extracts the reinforcing bar information stored therein. Further, since an opening list is linked to the object wall and the opening list describes that the opening Wall1 has the opening Open1, the structure output I / F 13A also extracts the attribute data of the opening Open1. The above data is shown in FIG. The structural output I / F 13A further obtains data on the columns C1 and C2, data on other members, frame information, and the like from the building model 15 if necessary.

As described above, the data of the opening Open1 includes the offsets x2 and h2 (the offset data has already been converted from x1, h1 to x by the design application 21A).
2, h2). This offset x2, h
In the building model 15, 2 is defined as the horizontal and vertical distance from the lower left corner of the wall Wall1 to the lower left corner of the opening Open1 as described above.

On the other hand, in the structural analysis application 22A, the position (offset) of the opening in the wall is defined with reference to the center of the column to which the wall is attached.
As shown in FIG. 15, an opening Open in the wall Wall1
The offset of 1 is the opening Open1 from the center of the lower end of column C1.
Are defined as the horizontal and vertical distances x01, h2 to the lower left corner of.

Since the definition of the offset in the building model 15 and the definition of the offset in the structural analysis application 22A are different, the structural output I / F 13A uses the offsets x2 and h2 obtained from the building model 15 under the definition in the structural analysis application 22A. A process of converting the value into a possible value is performed. The column C1 is accessed from the data of the column C1 stored in the wall Wall1, and the size data dx1 and dy1 stored therein are extracted. This data dx
1, dy1 represents the width of the pillar in two directions (see FIG. 15). Using one size data dx1, the offset used by the structural analysis application 22A is set to dx1 / 2 + x2
Is calculated as The thus calculated offsets x01 and h2 are passed from the structure output I / F 13A to the structure analysis application 22A. Of course, the structure output I / F
Other data extracted by 13A from the building model 15 is also converted as necessary, and then applied to the structural analysis application.
Handed over to 22A.

The structure analysis application 22A generates the data passed from the structure output I / F 13A and, if necessary, the data stored in the database or the necessary data, and executes the processing input in step 131. The stress calculation of the wall Wall1 is performed according to the conditions, the required wall strength is calculated, and the wall thickness required for the wall Wall1 is calculated from the required wall strength. It is assumed that the calculated wall thickness has a value d2 different from the wall thickness d1 read from the building model 15.

The structural analysis application 22A inputs the model data including the wall thickness d2 after the design change into the structural input I / F14.
Give it to A. The structure input I / F 14A converts the offset x01 of the data obtained from the structure analysis application 22A into a value x2 = x01-dx1 / 2 that can be accepted by the building model 15.
The structure input I / F 14A receives these changed data d.
2, the model data including the converted data x2, etc. is converted into the corresponding object, the wall Wall1, and the section Se in the building model 15.
c1, and stored in the opening Open1 and the like. In the building model 15, the wall thickness of the wall Wall1 in the model data is changed from d1 to d2 (see FIG. 16).

In general terms, when the structural analysis application 22A performs predetermined application processing relating to structural analysis, the result is passed to the structural input I / F (step 151).
At the same time, the data is output from the output device as needed (displayed on the display device) (step 133). Structure input I / F
14A performs processing such as converting the data passed from the structural analysis application 22A to the description format of the building model 15 for necessary ones (step 152), and writes it as attribute data of a corresponding object of the building model 15.

Structure output I / F 13A, structure input I / F 14A
When there is a difference in the description format of data between the building model and the application, as in the case of the conversion of the offset value, the output of the building information modeler and the input I / F are used for data conversion for matching the description format. Perform Specific examples of the data description format include a coordinate system such as the offset reference point described above, a data name (variable name), a data array (sequence) format, inches, meters, and millimeters. , Units such as Japanese and English, and those with different definitions (for example, when a rectangle is represented by the length of two adjacent sides,
In the case of expressing the coordinates by four points), one of them has no definition. When the description format is different from such a viewpoint, the output / input I / F converts the data in data transfer so as to match the description format of the partner to whom the data is to be delivered. If the description format is exactly the same between the building model and the application, data conversion is unnecessary.

In the above example, the wall thickness of the wall Wall1 was changed. If necessary, the design design application 21A is started again to redo the design design with respect to the wall Wall1, and the data on the wall Wall1 or the opening Open1 is passed from the building model 15 to the application 21A, and the design design is regenerated in the application 21A. Consideration will be given. In this way, the building model 15 that grows sequentially by the application processing in the application is displayed on the display device of the building information modeler 10 as necessary, and the user may appropriately confirm it.

The timing and manner in which the output I / F extracts data required by the application from the building model and passes the data to the application may have various forms. One of them is to collectively extract all data required by the application from the building model at the start of processing by the application and pass it to the application. The user activates the output I / F at the start of the processing by the application, and causes the output I / F to perform the above processing. Second, when required data is required in the course of processing of the application, the data is read from the building model and passed to the application. When any data is needed in the processing of the application, the user instructs the output I / F to take out the necessary data from the building model and pass it to the application. This is the case for the example described above. The data may be automatically transferred without requiring the user to operate the output I / F. The application requests necessary data from the output I / F.
The output I / F extracts necessary data from the building model according to this request and passes it to the application. The operation of writing the data of the processing result by the application into the building model by the input I / F may also be performed collectively.
It may be performed each time.

FIGS. 11 and 12 show the flow of data in both directions, that is, the operation of the output I / F and the operation of the input I / F. It is needless to say that there may be a unidirectional data flow in which data is passed to the application through the output I / F.

Various applications connected to the building information modeler 10 are generally independently developed and created. This is why the description format of data in a building model and the description format in various applications may be different (or more often). Therefore, it is generally necessary that an output interface provided between the building model and the application is created each time according to the application. It is up to the user to decide which application to use in the market or which application the user himself creates.
Assuming all types of applications, it is almost impossible to prepare input and output I / Fs in advance so as to be compatible with any application.

The data stored in the building model is also basically input by the user, and grows by using the building information modeler together with the application. It is almost impossible to provide the data in the building model in advance, and it is inappropriate.

Therefore, the building information modeler program
Preferably, it is provided as a tool that allows the user to most easily adapt to his or her application and to easily enter his or her own building data. This tool is generally FD (floppy disk), CD-R
It will be provided stored in a program recording medium such as OM.

The following programs are stored in the program recording medium as tools for constructing the building information modeler.

A database management system program for a building model, the above-described model editor and model viewer program, and a utility program (hereinafter simply referred to as a utility).

As described above, the utility is a component of the model editor and the model viewer program, and is used by the user to create an output and input I / F.

Tables 1 and 2 show examples of obtaining member information and setting member information among utilities.

[0102]

[Table 1]

[0103]

[Table 2]

FIG. 17 shows an example in which a part of the program of the structure output I / F 13A is created using a utility. This example uses the wall specifically described with reference to FIG.
Wall1 and its related data (section data, opening data) are acquired from the building model 15, and data is converted for the offset, and the structural analysis application 22A
This is the process to pass to. Underlined "aConstruction floo
“rAt:”, “aFloor wall”, etc. are instructions for calling the corresponding utility. This program is created by the user so as to be compatible with the structural analysis application 22A.

() Attached to the left side of the program code
The processing, meaning, and the like will be briefly described according to the line numbers in the parentheses.

In the line (1), a floor (floor) is specified. As a result, the attribute data of the designated floor is
Taken out of Specify the wall in line (2). As a result, a list of walls is extracted from the building model 15.

Lines (3) to (5) are instructions for extracting the name, thickness and section name of the wall.
Lines (6) to (8) are instructions to extract data on longitudinal, transverse and opening reinforcements.

Further, the names and sizes of the columns C1 and C2 related to the wall Wall1 are extracted by the instructions from the (9) th line to the (11) th line. These building models
The data extracted from 15 is the StructureData in the structural analysis application 22A by the statement in line (12).
It is stored in the file called. Above, the building model of the main data requested from the structural analysis application 22A
Removal from 15 ends.

Lines (13) to (15) are data conversion of offset values (x01 = dx1 / 2 + x2, h0 = h2 described above).
This is the program that performs the processing. Lines (16) to (18)
The shape wx2, wy2 of the opening Open1 is a building model 15 depending on the row.
Read from. The data related to the opening Open1 is also obtained from the StructureD by the instruction in line (19).
Discharged to the ata file.

FIG. 18 shows an example in which a part of the program of the structure input I / F 14A is created using a utility. This example relates to the example of FIG. 17, and is a process of returning the result of the strength calculation for the wall Wall1 executed by the structural analysis application to the building model 15.

Since the result of the application processing by the structural analysis application 22A is included in the StructureData file,
The process of acquiring the processing result data from this file is the second (2
From line 1) to line (30). The new wall thickness data and the new section data are stored in the corresponding locations of the building model 15 by the (30) th line and the (31) th line.

From line (32) to line (36), the offset value is inversely converted to the description format of the building model 15, and new opening data is converted into the building model 15 by lines (37) and (38). To be stored.

There are commercially available object data management systems (programs). When this commercial object data management system is used, the class of the building object model (for example, a site linked to a building, such as a site linked to a building) is stored in the program storage medium as a tool for building the building information modeler. (A coded description of the structure). If this class is read into a commercially available object data management system, an object data management system specialized for building models can be created.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a building model sharing system.

FIG. 2 is a block diagram illustrating a configuration of a building information modeler.

FIG. 3 shows an example of a building model.

FIG. 4 is a flowchart showing a procedure of model data input and editing processing.

FIG. 5 shows details of a pillar generation process.

FIG. 6 shows details of a wall generation process.

FIG. 7 shows an example of a model input / edit screen.

FIG. 8 shows another example of a model input / edit screen.

FIG. 9 shows an example of a screen for inputting attribute data of an opening.

FIG. 10 is a block diagram showing the configuration of a building model sharing system that employs design design and structural analysis as an application.

11 is a flowchart showing operations of a design design application, a design output I / F, and a design input I / F in the configuration of FIG. 10;

12 is a flowchart showing operations of a structure analysis application, a structure output I / F, and a structure input I / F in the configuration of FIG. 10;

FIG. 13 is a perspective view for explaining the meaning of data extracted from a building model.

FIG. 14 is a perspective view for explaining the meaning of data stored in a building model.

FIG. 15 is a perspective view for explaining the meaning of data extracted from a building model.

FIG. 16 is a perspective view for explaining the meaning of data stored in a building model.

FIG. 17 shows a specific example of a structure output I / F.

FIG. 18 shows a specific example of a structure input I / F.

[Explanation of symbols]

 10 Building Information Modeler 11,13 Output I / F 12,14 Input I / F 15 Building Model 21,22 Application

Claims (14)

[Claims] 1. A plurality of business support programs for at least some of a plurality of processes in a process from design of an object to management through manufacturing, wherein at least two of the programs have a description format of an object model. Differently, each business support program is in charge of one or more processes or a part of a process, and is a system for sharing the object model among a plurality of such business support programs. A database management system including a database for describing the object model in one format for a program and storing data representing the object model, and between a business support program and the database management system The data required for the business support program is provided from the database through the database management system. An output interface that acquires and converts the data into a description format compatible with the business support program; and an output interface provided between the business support program and the database management system. An input interface for converting the description into a descriptive format and writing the data in a corresponding location of the database through the database management system. 2. The object database management system is an object database management system, and a part of a utility program included in the object database management system is incorporated in the input / output interface. The system of claim 1. 3. The system according to claim 1, further comprising means for inputting data representing the object model into the database. 4. The system of claim 1, further comprising means for modifying data representing the object model in the database. 5. The system of claim 1, further comprising means for outputting and displaying data representing the object model in the database. 6. A plurality of business support programs relating to at least a part of a plurality of processes in a process from design of an object to manufacturing through management, wherein each business support program includes one or a plurality of processes or processes. Responsible for some,
This is a system for sharing the object model among a plurality of business support programs. The object model is described in one format for the plurality of business support programs, and the object model is described. A database management system including a database for storing data to be represented, means for inputting data representing the object model to the database separately from the business support program through the database management system, and An output interface that is provided between the business support program and the database management system, acquires data necessary for the business support program from the database through the database management system, and outputs the data to the business support program; With the system. 7. An input device, provided between a business support program and the database management system, for writing data generated by the business support program to a corresponding location of the database through the database management system. The system of claim 6, further comprising an interface. 8. The system of claim 1, further comprising means for outputting and displaying data representing the object model in the database. 9. An object model described in one format for sharing an object model among a plurality of business support programs is provided independently of the business support program, and is provided separately from the business support program. A method of inputting data to the object model, and exchanging data between the business support program and the object model via an interface. 10. A database which stores an object model described in one format shared by a plurality of business support programs and which is provided independently of the business support program. And a means for inputting data to the object model separately from the object model, and an interface for exchanging data between the business support program and the object model. 11. A database framework provided independently of the business support program for forming an object model described in one format shared by a plurality of business support programs, A program for inputting data to the database separately from the support program and a utility program for creating an interface for exchanging data between the business support program and the database are stored. recoding media. 12. The recording medium according to claim 11, wherein at least a part of the utility program is included in the framework of the database. 13. The data base framework according to claim 1, wherein
12. The recording medium according to claim 11, comprising a base management system. 14. The data base framework according to claim 1, wherein
The recording medium according to claim 11, which is a definition for a base management system.