Bridge component data automatic aggregation and reconstruction method oriented to multi-specialty collaboration

Abstract

The invention discloses a multi-specialty cooperation-oriented bridge component-based data automatic aggregation and reconstruction method, which is characterized by comprising the following steps of S1, independently defining and allocating a unique identifier to each component, and forcibly assigning a topological connection relationship of each component; according to the unique identifier, automatically retrieving and extracting all original data related to the component from a plurality of professional design tables of a plurality of design segments, and completing data aggregation across the design segments and across the professional tables; reconstructing a plurality of discrete data entries describing the same engineering entity into a single logic component object, and establishing a component-based topological data model; s2, based on the component-based data model obtained in the S1, generating a standard data table meeting downstream professional requirements; and S3, providing the standard data table to a downstream specialty through a standardized data interface, and driving a collaborative design process of the downstream specialty. According to the method, the problems of low collaboration efficiency and high error rate caused by data dispersion and model heterogeneity are solved.

Description

Technical Field

[0001] This invention relates to the field of computer-aided design and data management technology for bridge engineering, and in particular to a method for automatic aggregation and reconstruction of bridge component data for multi-disciplinary collaboration. Background Technology

[0002] In the design of large-scale bridge projects, multidisciplinary collaborative design has become the norm. However, the current collaborative design model faces three inherent challenges. First, due to the massive scale of bridges, the design work is often divided into multiple design segments, resulting in data describing the same bridge being physically scattered across different files. Second, data describing complete information about individual components is logically fragmented. For example, the type, curve parameters, quantities, and stiffness data of a bridge pier are stored in multiple heterogeneous professional tables such as the "Overall Bridge Design Table," "Curve Layout Table," "Quantity Table," and "Foundation Calculation Table."

[0003] The discrete tabular data model based on "pier numbers" used internally by bridge engineers for ease of calculation and drafting suffers from a severe structural mismatch with the holistic component model reflecting the engineering physical logic required by downstream disciplines. This mismatch forces bridge engineers to invest significant time in manual, repetitive cross-segment and cross-tabular data searching and reorganization to "feed" downstream disciplines. This process is extremely inefficient, taking 1-2 days without changes and requiring complete rework upon modification, and has become a major source of errors and delays in collaborative design. Therefore, there is an urgent need in this field for a systematic solution that can simultaneously address the problems of data dispersion, model heterogeneity, and semantic conversion. Summary of the Invention

[0004] To address the problems existing in the prior art, this invention provides an automatic aggregation and reconstruction method for bridge component data oriented towards multi-disciplinary collaboration, thereby solving the problems of low collaboration efficiency and high error rate caused by data dispersion and model misalignment in the prior art.

[0005] Therefore, the present invention adopts the following technical solution:

[0006] An automatic aggregation and reconstruction method for bridge component data oriented towards multi-disciplinary collaboration includes the following steps:

[0007] S1. Define each component independently, assign a unique identifier, and forcibly specify its topological connection relationship; based on the unique identifier, automatically retrieve and extract all original data related to the component from multiple professional design tables of multiple design segments, and complete data aggregation across design segments and cross professional tables; identify the extracted original data, and reconstruct multiple discrete data entries describing the same engineering entity into a single logical component object, and establish a componentized topological data model.

[0008] S2, based on the componentized data model obtained in S1, generates a standard data table that meets the needs of downstream professionals;

[0009] S3 provides the standard data table to downstream professionals through a standardized data interface, driving their collaborative design process.

[0010] In step S1 above:

[0011] The components include beam components, pier components, abutment components, and foundation components;

[0012] For beam members, specify the pier ID connected to its left end and the pier ID connected to its right end;

[0013] The unique identifier of each pier and abutment component is its own pier / abutment ID;

[0014] The unique identifier of the foundation component is its pier ID, and its foundation type is defined, including pile foundation, open-cut foundation, caisson foundation and excavated well foundation; for the pile foundation type, the number and quantity of the pile caps and each pile are specified, and the pile caps and all piles share the same pier ID.

[0015] In step S1 above: the professional design table includes a general design table for the entire bridge, a curve layout table, a quantity table for engineering works, and a foundation calculation table; the general design table for the entire bridge includes component types and bearing models; the foundation calculation table includes pier stiffness.

[0016] The reconstruction described in step S1 above specifically includes:

[0017] Continuous beam reconstruction: When the component type is identified as "continuous beam" from the overall bridge design table, the discrete data of these beam components are aggregated into a unified "continuous beam" logical object, skipping the intermediate piers and directly using the ID number of the first and last piers as the ID of the left and right piers.

[0018] T-shaped rigid frame reconstruction: When the component type is identified as "T-shaped" from the overall bridge design table, the data of multiple discrete components used to describe this structure are reconstructed into a unified "T-shaped rigid frame" logical object, which is directly associated with its left pier ID and right pier ID.

[0019] The standard data table mentioned in step S2 above is specifically as follows:

[0020] Bridge Span Style Table: By traversing all beam components and sorting them by their left-end pier ID, a table reflecting the layout of the entire bridge span is automatically generated; Pier Support and Stiffness Table: A table is automatically assembled by associating the support type of the beam components with the stiffness data of the pier components.

[0021] Compared with the prior art, the present invention has the following beneficial effects:

[0022] 1. The method of this invention completely liberates bridge engineers from tedious and inefficient manual data processing by automating cross-segment and cross-table data aggregation and reconstruction, greatly improving collaborative efficiency. Based on the method of this invention, other disciplines can directly extract the required data.

[0023] 2. The method of this invention fundamentally eliminates collaborative errors caused by misunderstandings of data structures by elevating discrete data into semantically clear componentized objects, ensuring the consistency and accuracy of design data. It intelligently reconstructs original, discrete data entries into a data model, dynamically generating various standard data tables required by downstream disciplines, and enables real-time data sharing and utilization through service interfaces, breaking down barriers from internal bridge design data to cross-disciplinary collaborative applications.

[0024] 3. The standardized and semantic data interface constructed by the method of the present invention lays a solid foundation for seamless integration and data interoperability between different professional design software, and powerfully promotes the improvement of the digitalization level of the entire bridge engineering industry. Attached Figure Description

[0025] Figure 1 This is a flowchart illustrating the overall process of the method of the present invention.

[0026] Figure 2 This is a schematic diagram of the componentized data model in an embodiment of the present invention;

[0027] Figure 3 This is a schematic diagram of the continuous beam polymerization process in an embodiment of the present invention. Detailed Implementation

[0028] The technical solution of the invention will be clearly and completely described below with reference to the accompanying drawings and embodiments. Obviously, the following embodiments are only some embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0029] This invention provides an automatic aggregation and reconstruction method for bridge component data oriented towards multi-disciplinary collaboration, such as... Figure 1 As shown, it includes the following steps:

[0030] S1. Construct a component-based bridge topology data model, including the following steps:

[0031] S11, Component definition.

[0032] Define the ID for each component (beam, pier, abutment, foundation component) and force the specification of its topological connection relationship, where:

[0033] For beam members, the pier IDs that are connected to their left and right ends are clearly specified respectively;

[0034] The unique identifier of each pier and abutment component is its own pier / abutment ID;

[0035] The unique identifier of the foundation component is its pier ID, and its foundation type is defined, such as pile foundation, open-cut foundation, caisson foundation and excavated well foundation; for pile foundation, the number and quantity of the pile caps and each pile are specified, and the pile caps and all piles share the same pier ID.

[0036] The pier ID uses the pier number from the original design system.

[0037] S12, cross-segment and cross-table data retrieval.

[0038] Based on the pier ID, all original data related to the component are automatically retrieved and extracted from multiple professional design tables across multiple design sections, completing data aggregation across design sections and professional tables.

[0039] The professional design tables include a total bridge design table (including component types and bearing models), a curve layout table, an engineering quantity table, and a foundation calculation table (including pier and abutment stiffness).

[0040] S13, Data Reconstruction.

[0041] Based on pre-defined engineering rules, the extracted raw data is identified, and multiple discrete data entries describing the same engineering entity are reconstructed into a single logical component object, establishing a componentized topological data model, specifically:

[0042] Continuous beam reconstruction: When the component type is identified as "continuous beam" from the overall bridge design table, the discrete data of these beam components are aggregated into a unified "continuous beam" logical object, skipping the intermediate piers and directly associating the ID numbers of the first and last piers as their left and right pier IDs.

[0043] T-shaped rigid frame reconstruction: When the component type is identified as "T-shaped" from the overall bridge design table, the data of multiple discrete components used to describe this structure in the traditional data model are reconstructed into a unified "T-shaped rigid frame" logical object. This object is directly associated with its left pier ID and right pier ID in the topological relationship.

[0044] S2, based on the componentized data model obtained in S1, generates a standard data table that meets the needs of downstream professionals, specifically:

[0045] Bridge span style table: By traversing all beam components and sorting them by their left-end pier ID, a table reflecting the layout of the entire bridge span is automatically generated;

[0046] Total bridge length: Automatically obtained by calculating the mileage difference between the first and last piers;

[0047] Pier Support and Stiffness Table: This table is automatically assembled by associating the support type of beam members with the stiffness data of pier members.

[0048] The componentized data model can directly generate the required standard data tables based on downstream professional needs.

[0049] S3 provides the standard data table to downstream professionals through a standardized data interface, driving their collaborative design process.

[0050] Example

[0051] In this embodiment, the track engineering specialty requests full bridge support and stiffness data. The specific steps for providing the data using the automatic aggregation and reconstruction method for bridge component data oriented towards multi-disciplinary collaboration provided by this invention are as follows:

[0052] S1, constructing a component-based bridge topology data model based on the full bridge structure.

[0053] like Figure 2 As shown, all the components of the bridge are abstracted and assigned unique identifiers (using the pier numbers):

[0054] Beam members: Define ID: The left end ID of a T-shaped rigid frame is 60, and the right end ID is 62. Define ID: The left end ID of a continuous beam is 33, and the right end ID is 36; Pier members: Define ID: 60, 62, and 33~36 are the IDs of the piers; Foundation members: Define ID: The foundation with ID 35 is a "pile foundation", and it is specified that it contains 1 pile cap and 12 piles (numbered 1-12).

[0055] Based on all component IDs, the component type and bearing model are automatically obtained from the overall bridge design table of segment A and segment B, and the pier stiffness is obtained from the foundation calculation table.

[0056] like Figure 3 As shown, the beam type of the left-end ID:33 is identified as a continuous beam, triggering the continuous beam reconstruction rule. These three data are aggregated into a logical object named L1 triple continuous beam, and its support data is taken as a set of key supports such as the first and last supports.

[0057] The component type of ID:60 on the left end is identified as "T-structure". The T-shaped rigid frame reconstruction rule is triggered, and the data that may have corresponded to multiple calculation units is reconstructed into a complete T-structure object (L2). Its support and stiffness data are treated as a whole.

[0058] S2 generates a standard data table, specifically:

[0059] Traverse all components, sort by the left-end ID of the beam, and automatically generate a bridge span style table: ... Beam 32—Beam 33—Beam 36—Beam 37—T-structure 60—Beam 62—...

[0060] The assembly yielded the pier support and stiffness table, with T-structure No. 60 appearing as a single unit, and its stiffness data directly related to the calculation of track forces.

[0061] S3, the collaborative data interface, automatically provides the generated standardized data tables to the design system for track engineering through a JSON / XML file or API response.

[0062] This embodiment clearly demonstrates how the method of the present invention can transform raw, discrete tabular data into a valuable and directly driven collaborative design information flow.

Claims

1. A method for automatic aggregation and reconstruction of bridge component data for multi-disciplinary collaboration, characterized in that, Includes the following steps: S1. Define each component independently, assign a unique identifier, and forcibly specify its topological connection relationship; based on the unique identifier, automatically retrieve and extract all original data related to the component from multiple professional design tables of multiple design segments, and complete data aggregation across design segments and cross professional tables; identify the extracted original data, and reconstruct multiple discrete data entries describing the same engineering entity into a single logical component object, and establish a componentized topological data model. S2, based on the componentized data model obtained in S1, generates a standard data table that meets the needs of downstream professionals; S3 provides the standard data table to downstream professionals through a standardized data interface, driving their collaborative design process.

2. The method for automatic aggregation and reconstruction of bridge component data according to claim 1, characterized in that, In S1: The components include beam components, pier components, abutment components, and foundation components; For beam members, specify the pier ID connected to its left end and the pier ID connected to its right end; The unique identifier of each pier and abutment component is its own pier / abutment ID; The unique identifier of the foundation component is its pier ID, and its foundation type is defined, including pile foundation, open-cut foundation, caisson foundation and excavated well foundation; for the pile foundation type, the number and quantity of the pile caps and each pile are specified, and the pile caps and all piles share the same pier ID.

3. The method for automatic aggregation and reconstruction of bridge component data according to claim 2, characterized in that, In S1: the professional design tables include a total bridge design table, a curve layout table, an engineering quantity table, and a foundation calculation table; the total bridge design table includes component types and support models; The basic calculation table includes the pier stiffness.

4. The method for automatic aggregation and reconstruction of bridge component data according to claim 3, characterized in that, The reconstruction described in S1 specifically includes: Continuous beam reconstruction: When the component type is identified as "continuous beam" from the overall bridge design table, the discrete data of these beam components are aggregated into a unified "continuous beam" logical object, skipping the intermediate piers and directly using the ID number of the first and last piers as the ID of its left and right piers. T-shaped rigid frame reconstruction: When the component type is identified as "T-shaped" from the overall bridge design table, the data of multiple discrete components used to describe this structure are reconstructed into a unified "T-shaped rigid frame" logical object, which is directly associated with its left pier ID and right pier ID.

5. The method for automatic aggregation and reconstruction of bridge component data according to claim 4, characterized in that, The standard data table mentioned in S2 is as follows: Bridge span style table: By traversing all beam components and sorting them by their left-end pier ID, a table reflecting the layout of the entire bridge span is automatically generated; Pier Support and Stiffness Table: This table is automatically assembled by associating the support type of beam members with the stiffness data of pier members.

Images