KR100848264B1 - Method for structuring database of steel bridge - Google Patents

Abstract

The present invention is a geometrical group grouping step for grouping the information of the geometric portion formed by the shape information of the steel bridge; A non-geographic portion grouping step for grouping non-geometric portion information including plan information, analysis information, and design information of the steel bridge; A connection relationship setting step of establishing a connection relationship between information of a geometric part and information of a non-geometric part; According to the connection relationship set by the connection relationship setting step, the information of the geometric part grouped by the geometric part grouping step and the information of the non-geometric part grouped by the non-geometric part grouping step are represented by a plurality of entities, By identifying the database construction method of the steel bridge, including the entity classification step to belong to the bridge (entertainment) bridge entity, to build a database based on the standardized information through the construction of an integrated environment for the steel bridge-related information do.

Steel bridge, database

Description

Database construction method of steel bridge {METHOD FOR STRUCTURING DATABASE OF STEEL BRIDGE}

1 to 16 illustrate an embodiment of a database construction method according to the present invention.

1 is a conceptual diagram of an information model of a geometric part.

2 is a conceptual diagram of an information model of a non-geometric part;

3 is a conceptual diagram of a data model development according to the ISO / STEP standard development methodology.

4 to 6 are flowcharts of information for each unit task in the design stage.

7 is a conceptual diagram relating to a bridge project overview.

8 is a conceptual diagram of a structure of a bridge component design entity.

9 is a conceptual diagram of the structure of a bridge member entity.

10 is a conceptual diagram relating to the structure of a shape entity.

11 is a conceptual diagram relating to the structure of a material entity.

12 is a conceptual diagram of the structure of a junction entity.

13 is a conceptual diagram relating to the structure of an application area entity.

14 is a block diagram representing the three-dimensional shape and design information of the NM1 section of Hannam Bridge.

15 is a block diagram representing the steel joints detailed information.

16 is a table showing a data model of the Hannam Bridge in a STEP file.

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to the field of construction, and more particularly, to a method for constructing a database of steel bridges in which shape information, design information, and the like of steel bridges can be easily used.

Over the past decade, engineers working in each industry have built an integrated environment to enable effective work using a variety of information technologies.

In particular, as a core technology for building an integrated environment among various information technologies, the core competency is administered to establish an integrated database and a system for exchanging and sharing product model data in an electronic format.

Already, the automotive, aerospace and marine industries have been very successful in exchanging and integrating product data generated based on electronic product model standards.

For example, the AutoSTEP project integrates product information and process information between automotive manufacturers and partners by applying the ISO / STEP standard, which enables accurate and economical exchange of product data and concurrent engineering. It provided a system that can perform collaboration work collaboratively.

The construction industry is based on the information system in the form of two-dimensional drawings and paper documents, occurs in the whole life cycle of the project because several decentralized organizations participate in one construction project and are frequently redesigned. There is an urgent need to develop standards for electronically exchanging and sharing information.

The construction industry has also been making efforts to exchange electronic data. In the construction industry, the development of standards for electronically exchanging relevant data began around 1986, and research was activated, starting with Gielingh and Turner's thesis.

In particular, Gielingh proposed a model called GARM (General AEC Reference Model).

GARM was used as the foundation model for the development of the Integration Core Model (ICM) in the CAM-I project. In practical modeling, GARM influenced the construction industry's development of data models for many years, although relatively limited.

After the GARM, in 1990, many researchers proposed a new model called the Integration Reference Model AEC (IRMA). In a paper by Luijten et al, the IRMA model still incorporates some features of GARM.

The IRMA model, through the analysis of several experts, extended the scope of the product model to PROJECTS and composed the basic entities of PROCESSES, RESOURCES and CONTROLS. The four basic entities presented by IRMA were used as root entities for construction.

Recently, in the construction industry, efforts to build a computer integrated construction (CIC) environment through the development of data models of steel-framed buildings and bridge structures are showing various results.

For example, Crowley and Watson developed a CIS / 2 (CIMsteel Integration Standards) model based on a standard data model development methodology to manage and share information between organizations involved in the planning, analysis, design and construction of steel frame structures. It was. Currently, the CIS / 2 model has been adopted as an international standard in Europe and is used in practical work.

On the other hand, there is a case where a database is constructed for the bridge structure only by Mikami et al. For the shape information of the bridge structure.

In addition, Tah and Howes used a case-based reasoning technique to build a data model that can store knowledge from previous projects so that they can apply the information from previous bridge projects and apply them to new projects. However, the research on the construction of a data model including actual engineering information by constructing a model with information on the progress of the project is still insufficient.

The present invention has been made to solve the above problems, to provide a database construction method of the steel bridge to build a database based on the standardized information for the construction of an integrated environment on the steel bridge related information. It is done.

The present invention, the geometric portion grouping step for grouping the information of the geometric portion constituted by the shape information of the steel bridge in order to achieve the object as described above; A non-geographic portion grouping step for grouping non-geometric portion information including plan information, analysis information, and design information of the steel bridge; Establishing a connection relationship between the information of the geometric part and the information of the non-geometric part; According to the connection relationship set by the connection relationship setting step, the information of the geometric portion grouped by the geometric portion grouping step and the information of the non-geographic portion grouped by the non-geometric portion grouping step are expressed as a plurality of entities, A method of constructing a database of steel bridges is provided.

The bridge entity is preferably configured to refer to a superstructure entity representing attribute information for the superstructure of the steel bridge, and a substructure entity representing attribute information for the substructure of the steel bridge. Do.

The bridge entity preferably includes a bridge outline entity having at least one of the name, length, width, location, and management of the steel bridge.

Preferably, the positional information of the steel bridge provided in the bridge outline entity is expressed by three-dimensional coordinate values.

The bridge outline entity preferably includes a structural outline entity that represents information about design criteria and design loads applied to the structural design of the steel bridge.

The bridge entity preferably includes a bridge component entity that represents a major component of the steel bridge.

The bridge component entity includes a superstructure entity representing attribute information of the superstructure of the steel bridge and a substructure entity representing attribute information of the substructure of the steel bridge. desirable.

The superstructure entity may be a primary member entity representing attribute information of a main member constituted by a slab and a bending member, and a subsidiary member expressing attribute information of a member other than the main member. secondary member) entity.

Preferably, the primary member entity expresses attribute information of at least one member among girders, stringers, and horizontal beams.

The secondary member entity preferably represents attribute information of at least one member of a stiffener, brace, and diaphragm.

The slab entity included in the main member entity preferably represents attribute information of at least one member of a pavement, deck, expansion joint, and separator.

Preferably, the substructure entity expresses attribute information of at least one member among shifts, piers, shoes, foundations, and files.

The bridge entity preferably includes a bridge component entity representing detailed design information of the members constituting the steel bridge.

The bridge component entity preferably includes a part entity representing the member of the steel bridge and an assembly entity representing a combination of the members of the steel bridge.

The assembly entity includes a parts assembly entity for expressing a combination of components among the parts of the steel bridge, and an assembly assembly entity for expressing a combination of assemblies among the parts of the steel bridge. desirable.

The bridge entity preferably includes a shape entity representing the geometry of the steel bridge.

The shape entity may include a plurality of shape definition representation entities representing the three-dimensional shape of the steel bridge by a CSG (Constructive Solid Geometry) method and a landmark method, or cross-sectional properties of the center line and the member. It is preferred that it is defined to refer to an entity having a linear member with the same.

The shape entity preferably includes a simple shape entity representing cross-sectional information for the linear member of the steel bridge having the centerline.

The simple shape entity may be an angle shape entity, a rectangle shape entity, a channel shape entity, a circle shape entity, a h shape entity, t It is preferable to include at least one or more of a t shape entity, an i shape entity, a box shape entity.

The shape entity preferably includes a complex shape entity that represents a complex shape other than the shape represented by the simple shape entity.

The complex shape entity preferably includes a bolt shape entity, a nut shape entity, and an arbitrarily shape entity.

The arbitrarily shape entity preferably comprises an arbitrarily shape with void entity.

The bridge entity preferably includes a material entity for defining the properties of the material used in the absence of the steel bridge.

The material entity has a thermal expansion property expressing the coefficient of thermal expansion, an elasticity property expressing the elastic modulus, a poisson ratio property expressing the Poisson's ratio, and a self-weight expressing self-weight. It is desirable to define the properties of the material using at least one or more of the weight density properties.

The material entity preferably includes a steel material entity representing the properties of the steel and a concrete material entity representing the properties of the reinforced concrete member.

The concrete material entity preferably represents at least one or more properties of the strength of the concrete, the shear strength of the concrete, the yield stress of the reinforcement, and the yield stress of the shear reinforcement in the reinforced concrete member.

The bridge entity preferably includes a joint system entity for defining the properties of the joint of the steel bridge.

The joint system entity preferably includes a joint system mechanical entity representing a mechanical joint structure, and a joint system welded entity representing a weld joint structure.

The bridge entity preferably includes an application context entity that represents at least one or more attributes of the application area, field of application area, life cycle stage, customer layer, and specification of the steel bridge.

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

The present inventors can conduct the early stage research on the development of information model and database construction based on ISO / STEP for steel bridge structures, and exchange and share information according to ISO / STEP standard based on the design information of steel bridge structures. It has been proven.

Therefore, in this embodiment, the structure of the structure is based on the three-dimensional shape information using the ISO / STEP standard, which is an international standard for product information, in order to establish an integrated environment by exchanging and sharing information generated in the life cycle of steel bridge projects. Design information, property information and project information are expressed.

In this embodiment, the data model is developed by dividing the geometric and non-geometric parts to effectively represent the design information of the steel bridge. The geometric information is represented as a three-dimensional solid model by the Boundary RePresentation method using Part 42 (geometric and topological representation) provided by ISO / STEP so that existing information can be reused. The information presented in the EXPRESS language describes the information requirements analyzed in accordance with the standard data model development methodology.

In order to verify the EXPRESS schema of the developed data model, this example examined the validity of the syntax and reference of the model developed using the EXPRESS Engine. In order to verify whether it is possible to express, the validity of the model was verified by storing the design information of Hannam Bridge in the database.

In this embodiment, two approaches were applied to develop a data model for representing three-dimensional shape information, plan information, analysis information, and design information of a structure in the life cycle of a steel bridge.

The first approach is to develop a data model by applying the product structure defined in the manufacturing industry to steel bridge structures, as shown in FIGS.

That is, FIG. 1 shows the three-dimensional shape information of the steel plate bridge upper structure among the steel bridge structures according to the structure of the product, and FIG. 2 shows the design information of the structure based on the structure of the product. In this paper, we developed a data model to express the design information of steel bridges by establishing the connection relationship between three-dimensional shape information and design information of the subdivided steel bridges.

In this approach, the design information of the steel bridge is expressed in the form of assembly of members corresponding to a single part of the product, which enables flexible information expression during data model development.

The second approach is to develop a data model using the standard data model development methodology proposed by ISO / STEP and the application protocols used as international standards.

3 is a schematic diagram of a data model development methodology of ISO / STEP. The data pool is extracted by extracting information requirements calculated through process analysis and design information of a steel bridge considered to be a product. It was configured.

Based on the description method suggested by STEP methodology, the constructed data pool expresses the design information including the three-dimensional shape information of the steel bridge in EXPRESS language by establishing the relationship between the entity and the entity.

As such, the data pool containing design information separates pure three-dimensional shape information as shown in FIG. 3 according to the approach of subdividing the design information of the steel bridge into geometric information and non-geometric information as described in FIG. Replaced with AP 203 (configuration controlled design) EXPRESS schema, and the data model of the remaining parts except 3D shape information was expressed as EXPRESS schema through linkage between design information of steel bridge and 3D shape information.

This approach allows the use of three-dimensional shape information generated by existing CAD / CAE / CAx tools.

In this embodiment, since the existing design information in the construction industry is managed and operated mainly on two-dimensional drawings, it is almost impossible to create added value through the practical use of design information. Represented as a dimensional solid model, it was possible to link shape information with design information.

In this example, the flow of work and information that occurs during the entire life cycle of a steel bridge project, that is, during the planning, design, construction / supervision, and maintenance phases, is developed in the IDEF0 methodology. Based on this analysis, a process model was defined.

In particular, in order to analyze the flow of information generated in the design process and to determine the range of information to be included in the data model among the entire work processes of the bridge, this embodiment shows the information flow for each unit task in the design stage in FIGS. It was.

In this example, the bridge's business process model is defined using KBSI's AI0 Win program, which implements the IDEF0 methodology as a tool.

The ISO / STEP methodology defines information requirements to define the scope of information from these process models to be included in the data model.

The information requirements indicate the correlation between the data to be included in the data model and each data. In this embodiment, the information requirements are configured as a data pool using the EXPRESS language and used as data to be processed in the data model.

In this example, the data model was developed by dividing the data model into seven submodels using the two approaches mentioned above to represent the steel bridge structure.

The seven submodels developed include information from the planning stage, analysis stage, and design stage of the lifecycle of steel bridge structures.

That is, the information generated in the construction and maintenance phase is not included in the scope of the present invention.

In particular, since the information generated in the maintenance phase is being operated by the existing bridge management system (BMS) in the present embodiment was developed based on the standard exchange technology such as STEP in consideration of the linkage with the existing system.

The PROJECT model defined general overview information of steel bridge project, overview information and design information of steel bridge structure.
The above-described "connection relationship setting step of setting the connection relationship between the geometric part information and the non-geometric part information" means a component of a bridge to which non-geometric part information and geometric part information can be mapped to each other. A step for finding an entity to be referred to, and specific details of an entity meaning a component of a bridge that can be mapped to each other are as follows.

In FIG. 7, the bridge entity is divided into steel and concrete according to the material used as the highest entity for information expression of the bridge structure, and superstructure entities are listed to express attribute information on the superstructure of the steel bridge. We defined to refer to by value form, and to define information about substructures, we defined to refer to substructure entities in list value form.
Here, the "property information" refers to information for expressing components, shapes, and material information constituting an entity described later.

In the future, the location attribute value in the bridge outline entity was expressed in three-dimensional coordinates so that the steel bridge information could be linked to the national geographic information system that is actively promoted by the government.

In addition, the structural outline entity, which inherits the bridge outline entity, expresses information about various design criteria and design loads applied to the structural design.

Bridge entities representing the overall structure information of steel bridges are defined to include design information for superstructures and substructures.

The bridge component model defines the main elements constituting the steel bridge structure, and in this embodiment, the bridge component entity is divided into a superstructure and a substructure as shown in FIG. 8. .

In this embodiment, the superstructure is defined as a slab and a primary_member designed primarily to resist warpage and a secondary_member entity for bracing between the main members.

Substructures were defined as abutments, piers, shoes, footings, piles, and pedestals.

The data model defined in this example classifies the main members constituting the steel bridge structure into 16 and does not consider the classification of the detailed members.

However, the definition of the detailed members of the steel bridge structure is defined in the bridge member entity referred to in the member property of the bridge component so that all members of the steel bridge can be defined.

Because the bridge component entity is a top-level entity that indicates the absence of the bridge structure described above, the entity definition part specifies that the actual data value cannot be defined using the ABSTRACT keyword.

The superstructure entity representing the superstructure is defined in the structural type attribute to define the structural form of the superstructure.

In the present embodiment, the super structure type corresponding to the structural type attribute value is a steel box girder bridge or steel plate type, which is the most representative structural type of the steel bridge. Steel plate girder bridge and truss bridge.

Since these three structural forms consist of steelwork produced by factory production, it was possible to apply the product structure system adopted in the data model development in the present invention.

The bridge member model is defined to represent detailed design information of the detailed members included in the eight members classified in the bridge component model.
Here, the "detailed design information" refers to information on the components constituting the member or structure, information representing the 3D shape of each component, and material information of the components.
For example, in the case of steel joints of steel bridges, it means detailed design information such as the spacing between bolts and the welding method based on bolts, nuts and washers.

As defined in FIG. 9, a bridge member entity is composed of an assembly entity representing a combination of members and a part entity representing a member, and the life cycle stages of the structure in the frame of reference attribute. Expressed.

The part entity that defines the parts that make up the structure is defined by the part_name attribute representing the part name and the part_type attribute representing the type of the part, and also can include multiple shape entities representing the three-dimensional shape of the part. We have defined the components property.

For example, the mold of a steel box bridge consists of n flanges, webs, and ribs. The n steel plates that make up the mold can be represented by n three-dimensional solids consisting of points, lines, and faces, and the defined n solids information is included in the component properties of the part entity. The three-dimensional shape of the template can be expressed.

The assembly entity representing the combination information of the members is represented as an assembly assembly entity representing a combination between the parts assembly and the parts assembly entity representing the combination between the members.

Parts assembly The entity is expressed to include a part entity in the form of a list value in the parts attribute, so that the connection between mold members on the same line can be represented.

The data model for finite element analysis defined in composite and metallic structural analysis and related design (AP209) of ISO / STEP was used to describe the structural analysis of steel bridge structures.

That is, the connection between the structural design member of the structure and the structural analysis information is made by defining a correlation between the element_representation entity of the AP209 and the bridge member entity in the member_element_map entity of FIG. 9.

Here, the element_representation entity is an analysis element used in defining the structural analysis model and is represented by volume, surface, curve, and point elements, and represents a discretized part of the continuum connected to the node to model the continuum to be analyzed. .

Many of these elements have different characteristics for different continuum models.

This linkage still contains the problem that the structural analysis information according to the individual engineer's modeling and the design information determined through the design stage are not completely matched when defining the structural analysis model.

That is, structural design information can be expressed as only one information, but structural analysis information can be modeled by various analysis models, so that the geometric shape defined in the modeling process and the geometric shape of the actual design member are different.

However, it is useful in terms of managing and operating structural analysis information in an integrated database.

The shape (SHAPE) model is defined to represent the geometry of the steel bridge structure based on the three-dimensional shape information represented by the solid model. All property information of the steel bridge structure defined in the present invention is configured to be defined in connection with the shape information represented by the three-dimensional solid model.

As shown in FIG. 10, the shape entity, which is the highest entity of the shape model, is defined to refer to a plurality of shape definition representation entities by the solid_shape attribute value. That is, it is possible to express in one shape by combining several shapes.

The shape_definition_representation entity is an entity included in AP203, an application protocol of STEP, and expresses the shape of a three-dimensional solid model in CSG (Constructive Solid Geometry) and landmark representations.

In the present embodiment, it is expressed according to the landmark present method which is widely used for representing 3D solid model information.

The landmark chord method is to create a three-dimensional shape with the orientation of the faces after composing the face with a combination of sides, and define all faces counterclockwise to the edge of the edge to obtain a normal vector, The direction is defined to define the inside and outside of the face.

Therefore, in the present embodiment, by expressing the bridge information based on the two-dimensional drawing information based on the three-dimensional shape information, not only the recognition of the information is performed by a person but also the information can be recognized by a computer.

In addition, the information required by the user is easy to access and the administrator can easily maintain the information.

The simple shape entity inherits the solid model information from the shape entity, which is the parent entity, and expresses the cross-sectional information of the linear members of the structure. The shape of the member forming the steel bridge structure is an angle shape. Entities, Rectangle Shape Entities, Channel Shape Entities, Circle Shape Entities, h Shape Entities, t Shape Entities, i Shapes, Boxes It is represented by eight sub-entities of a box shape entity.

The complex shape entity represents a member that is difficult to express only by cross-sectional information and is defined as three sub-entities.

In other words, the bolt constituting the joint is defined as a bolt shape entity and the nut is a nut shape entity, and in the case of having an arbitrary cross-sectional shape, it can be represented by using an arbitrary shape entity. .

Therefore, the bottom plate of the superstructure can be represented by using an arbitrary shape entity.

In the present embodiment, a member made of concrete such as a bottom plate, a pier, a shift, and a foundation includes only three-dimensional shape information and outline information.

The MATERIAL model is a model for defining the characteristics of materials used in the members of the structure. In this embodiment, the MATERIAL model is divided into steel, concrete, and user-defined materials.

As shown in FIG. 11, the material entity has a thermal expansion property expressing a thermal expansion coefficient, an elasticity property expressing an elastic coefficient, a poisson ratio property expressing a Poisson's ratio, and a self-weight expressing self-weight ( The weight density properties were used to define the material properties of the members and to further expand the required physical properties.

The steel material entity, the concrete material entity, and the user_defined_material entity that inherit the material entity are the entities that represent the properties of the material required during the design phase of the life cycle.

Steel material entities contain property values for expressing the yield stress of steel, etc. Concrete material entities are concrete strength, shear strength of steel, yield stress of steel and shear reinforcement in reinforced concrete members. It is defined to include yield stress value of.

Material entities are information that exists independently of the bridge's design elements.

Therefore, part_element_map entity is defined to connect material property and design element. Part_element_map entity is defined to have several material entities including material properties and part entities expressing member information of design elements.

The joint system model represents the joint of the structure, and the joining method is defined as a welding method and a mechanical method.

As shown in FIG. 12, the joint system entity may represent the design member to which the joint is to be made by defining the connected_assembly attribute value as a parts assembly entity in the highest entity representing the joint.

The joint system mechanical entity that defines the mechanical joint method is defined to have a plurality of shape entities in the components property representing the shape information. In the mechanism property, the mechanical joint type is defined by referring to the joint_system_mechanical_type type. The range was limited to pin and rivet joints.

Therefore, the joint system mechanical entity expresses the joint connection by a mechanical method and binds the bolts, nuts, washers, and steel sheets, which constitute the joint, as a joint member.

The joint information by welding is shown in the joint system welded entity, and the sub-entity is represented by subdividing it into point, line, and face welding according to the welding type.

In particular, the weld_specification attribute of a weld system welded entity expresses information about a welding method and a penetration range.

The application context model uses the application_context_schema of ISO10303 Part 41 as shown in FIG. 13. This model provides an entity that represents the application domain, the discipline of the application, the lifecycle stage, the market segment, and the library of product specifications that you want to define as an application domain schema.

An application context (Application_context) entity is an area where product data is defined. It affects the use and meaning of product data and expresses various types of information related to product data. In this embodiment, AP203 is adopted to represent the three-dimensional shape of the steel bridge structure and AP209 is used to represent the structural analysis information. Therefore, the application_protocol_definition entity is used to use multiple data models.

Since this entity specifies the application protocol used to represent the product information, it can be specified that the AP203 schema is used for the three-dimensional shape information of the steel bridge and the AP209 schema for the structural analysis information.

In addition, in this embodiment, the product_definition_context entity is used to represent the life cycle stage of the product information generated in the steel bridge structure.

The verification of the developed data model was carried out by dividing the conformance verification part of the syntax of the EXPRESS schema and the applicability verification part of the developed model by inputting the actual physical data values.

For the verification of the EXPRESS schema syntax of the steel bridge data model, the EXPRESS parser of the EXPRESS Engine, which is freely provided by the National Institute of Standards and Technology (NIST), was used.

In addition to reviewing the EXPRESS schema format, the EXPRESS Engine is a tool that provides the ability to create a physical file according to ISO / STEP Part 21 (clear text encoding of the exchange structure) and to review various constraints defined in the schema. In addition, the EXPRESS schema of the developed steel bridge data model is reviewed for validity of syntax and references according to the conformance classification criteria presented in the EXPRESS Language Reference Manual, and for types and values that meet certain conditions.

In this example, the suitability of the data model developed for the above-mentioned matters was verified through the above EXPRESS Engine.

In order to verify whether the developed data model is able to represent the information of the actual steel bridge structure, various information of Hannam Bridge, the first-class bridge on the Han River in the form of steel girders, is matched with the structure of the developed data model. Shown in the file.

FIG. 14 shows the three-dimensional shape and design information of each shape of the NM1 section, which is the first span among the seven spans of the Hannam Bridge.

The upper structure of Hannam Bridge NM1 section is steel plate type girder type and can be adopted as an example for verification of conformity of the data model developed in the present invention.

First, referring to the structural design information in the STEP physical file represented in the table of FIG. 16, # 32 and # 33 of FIG. 14 represent stringers of the Hannam Bridge NM1 section, and # 41, # 42, and # 43 are horizontal beams. As a cross beam, it was possible to express using a part entity among the entities of the developed model.

# 36, # 46 and # 47 represent the splices by bolts and can be expressed as a joint system entity.

Therefore, in Table 1, structural design information corresponding to # 32 and # 33 of FIG. 14 and # 36 as a junction part among the several design members are expressed in STEP physical file format.

FIG. 15 is a representation of the three-dimensional shape and the member specifications of the longitudinal beams corresponding to the design information of # 32 and # 33 and the joint of # 36, and is a STEP file using part entities and related entities of the developed model. Can be expressed.

In the STEP file of FIG. 16, # 32 indicates that the member type is represented by .STRINGER. To represent a column beam, and that the member name is 'NM1-stringer1', and the shape information related to the member corresponds to # 200 and # 201. Could be expressed as.

For example, # 200 represents a data value having a rectangular cross-sectional shape using a rectangle_shape entity, and expresses information of # 32 having a cross-sectional thickness of 12.0 mm and a width of 400.0 mm.

# 36 of FIG. 15 represents a joint of the stringer corresponding to the design information by using a joint system entity and related entities.

As shown in FIG. 15, the fastener used in the joint was a bolted joint, and thus could be represented as a joint system mechanical entity.

# 36 in FIG. 16 is represented by .BOLTED_TYPE., Indicating that the joining method is a bolted joint, and that the shape information constituting the joint is # 206, # 210, # 212, # 213, and # 220.

Here, # 220 represents the shape and specification information of the bolt, and it is a high-strength bolt by .HIGH_STRENGTH_BOLT. It indicates that the bolt radius is 10mm.

The Hannam Bridge information expressed based on the PROJECT model is a representative case, and the general outline information of the project is shown in # 12, and the outline information of the structure is also shown in # 13.

This summary includes design criteria and design loads in # 21, # 22, # 23, and # 24. Next, the steel plate of the first section of Hannam Bridge was expressed as .STEEL_PLATE_GIRDER based on the COMPONENT model representing the main elements of the structure. In addition, a MATERIAL model representing the material properties is shown in # 50.

Finally, the relationship between structural design information and structural analysis information in STEP file is represented in # 1500 according to APPLICATION CONTEXT model. And, in # 13877, the analysis element of the analysis information connected with the structural design member is represented by the three-dimensional curve element.

The structural analysis information linked with the design information is represented by the application_protocol_definition entity of # 5 because it is built on the ISO / STEP AP209 EXPRESS schema. Indicated.

Through this process, it was proved that the steel bridge data model developed in the present invention can express the project outline, three-dimensional shape, structural analysis and design information generated in Hannam Bridge.

Since the above has been described only with respect to some of the preferred embodiments that can be implemented by the present invention, the scope of the present invention, as is well known, should not be construed as limited to the above embodiments, the present invention described above It will be said that both the technical idea and the technical idea which together with the base are included in the scope of the present invention.

The present invention proposes a method for constructing a database of steel bridges to build a database based on standardized information in order to build an integrated environment related to steel bridge-related information.

The present invention relates to a data model for representing the design information of the steel bridge based on the three-dimensional solid model to integrate and operate the information generated in the steel bridge.

In the development of the data model, the common resources of ISO / STEP were used to represent the three-dimensional shape information of the steel bridge, so it was possible to use the results of the existing commercial CAD / CAD / CAx program.

In addition, a data model was developed by applying the product structure defined in the manufacturing industry to steel bridge structures.

That is, the three-dimensional shape information of the steel bridge structure is subdivided according to the product structure system, and the design information of the structure is subdivided into single parts and assemblies based on the product structure system. The design information of the steel bridge was expressed by establishing the connection relationship between the information.

The defined design information is divided into geometric part and non-geometric part, and geometric part is expressed by using resources of STEP, and non-geometric part is connected with geometric part.

In this approach, the design information of the steel bridge is expressed in the form of assembly of members corresponding to a single part of the product, which enables flexible information expression during data model development.

Syntax verification for the EXPRESS schema of the developed data model is performed by examining the validity of the syntax and references according to the conformance classification criteria of the model presented in Part 11 of ISO / STEP using the EXPRESS Engine provided by NIST. The suitability of the data model was verified by examining whether the conditions were met.

Also, to verify whether the developed data model can represent the design information of the actual steel bridge structure, the validity of the data model was verified by applying the actual physical data values to the Hannam Bridge.

Through this process, it was possible for the steel bridge data model developed in the present invention to express project overview information, structure shape information, analysis information, and design information of the Hannam Bridge.

The data model developed in the present invention provides a basis for building an integrated environment by enabling the exchange and sharing of information generated in the life cycle of steel bridge projects using ISO / STEP.

Claims (28)

A geometric portion grouping step of grouping information of the geometric portion constituted by the shape information of the steel bridge; A non-geographic portion grouping step for grouping non-geometric portion information including plan information, analysis information, and design information of the steel bridge; Establishing a connection relationship between the information of the geometric part and the information of the non-geometric part; According to the connection relationship set by the connection relationship setting step, the information of the geometric portion grouped by the geometric portion grouping step and the information of the non-geographic portion grouped by the non-geometric portion grouping step are expressed as a plurality of entities, An entity classification step of belonging to a bridge entity which is a top-level entity; Database construction method of the steel bridge, including. The method of claim 1, The bridge entity A method for constructing a database of steel bridges, comprising: referencing a superstructure entity representing attribute information of the superstructure of the steel bridge and a substructure entity representing attribute information of the substructure of the steel bridge . The method of claim 2, The bridge entity And a bridge outline entity having at least one information of a name, length, width, position, and management authority of the steel bridge. The method of claim 3, And the position information of the steel bridge provided in the bridge outline entity is expressed by three-dimensional coordinate values. The method of claim 3, The bridge outline entity And a structural outline entity representing information on design criteria and design load applied to the structural design of the steel bridge. delete The method of claim 1, The bridge entity comprises a bridge component entity, The bridge component entity And a superstructure entity expressing attribute information of the superstructure of the steel bridge, and a substructure entity expressing attribute information of the substructure of the steel bridge. The method of claim 7, wherein The superstructure entity It includes a primary member entity representing the attribute information for the main member composed of the slab and the bending member, and a secondary member entity representing the attribute information for the member other than the main member A method of constructing a database of steel bridges. The method of claim 8, And wherein the primary member entity represents attribute information of at least one member among girders, stringers, and crossbeams. The method of claim 8, And said secondary member entity expresses attribute information on at least one member of a stiffener, brace, and diaphragm. The method of claim 8, A slab entity included in the main member entity expresses attribute information on at least one member of a pavement, deck, expansion joint, and separator. The method of claim 7, wherein The substructure entity is A method for constructing a database of steel bridges, characterized by expressing attribute information of at least one member among shifts, piers, shoes, foundations, piles, and pedestals. The method of claim 1, The bridge entity And a bridge component entity for expressing detailed design information of a member constituting the steel bridge. The method of claim 13, The bridge component entity And a unit entity representing a member of the steel bridge, and an assembly entity representing a combination of the members of the steel bridge. The method of claim 14, The assembly entity is A database of steel bridges, comprising: an assembly assembly entity expressing a combination of components among the parts of the steel bridge, and an assembled assembly entity expressing a combination of assemblies among the parts of the steel bridge; Way. The method of claim 1, The bridge entity And a shape entity representing the geometry of the steel bridge. The method of claim 16, The shape entity A plurality of shape definition representation entities expressing the three-dimensional shape of the steel bridge by a CSG (Constructive Solid Geometry) and a landmark representation, or an entity having a linear member having a cross-sectional property of a center line and a member. Database construction method of steel bridges, characterized in that defined for reference. The method of claim 17, The shape entity And a simple shape entity representing cross-sectional information of the linear member of the steel bridge having the center line. The method of claim 18, The simple shape entity Angle shape entity, rectangle shape entity, channel shape entity, circle shape entity, h shape entity, t shape entity, i A method of constructing a database of steel bridges comprising at least one of an i shape entity and a box shape entity. The method of claim 18, The shape entity And a complex shape entity that represents a complex shape other than the shape represented by the simple shape entity. The method of claim 20, The complex shape entity A method of constructing a database of steel bridges comprising a bolt shape entity, a nut shape entity, and an arbitrary shape entity. The method of claim 1, The bridge entity And a material entity for defining properties of the material used in the absence of the steel bridge. The method of claim 22, The material entity is At least one of a temperature expansion property expressing the coefficient of thermal expansion, an elasticity property expressing the elasticity coefficient, a poisson ratio property expressing the Poisson's ratio, and a weight density property expressing the self-weight A method for constructing a database of steel bridges, characterized by defining the properties of the material using one or more. The method of claim 22, The material entity is A method of constructing a database of steel bridges, comprising: a steel material entity expressing the properties of the steel, and a concrete material entity expressing the properties of the reinforced concrete member. The method of claim 24, The concrete material entity A method for constructing a database of steel bridges, characterized by expressing at least one of the properties of concrete, shear strength of concrete, yield stress of reinforcement, and yield stress of shear reinforcement in reinforced concrete members. The method of claim 1, The bridge entity And a joint system entity for defining characteristics of the joint of the steel bridge. The method of claim 26, The joint system entity is A method of constructing a database of steel bridges comprising a joint system mechanical entity representing a mechanical joint structure, and a joint system welded entity representing a weld joint structure. delete

Images