BIM Minimum Unit Data Integration System, Method, and Apparatus Based on Digital Model Separation

By using the digital-model separation technology, the association identification and coding of model components are established, and lightweight models and standardized data records are generated. This solves the problem of component identification changes and data association after the BIM model is lightweighted, realizes independent updates and efficient management of model and business data, and improves the stability and sharing capabilities of engineering data.

CN123114425APending Publication Date: 2026-11-17XIDI (SUZHOU) SURVEY & DESIGN CONSULTING CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611322095.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-28
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, component identification in BIM models is prone to change after lightweighting, making it difficult to maintain a continuous connection between the model and business data. Updates require synchronization, and multi-source engineering data is difficult to manage uniformly at the smallest model unit level.

Method used

By employing the model-data separation technology, lightweight models and standardized data records are generated by establishing association identifiers and codes for model components. These are then processed and updated independently. An association engine is used to establish the association relationship between the smallest model unit and the data record, thereby achieving decoupled management of the model and business data.

Benefits of technology

It improves the efficiency of engineering data management, ensures the stability and reliability of relationships during model transformation, realizes continuous integration and consistency management of engineering data throughout its entire lifecycle, reduces computational overhead, and improves data management granularity and sharing capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123114425A_ABST
    Figure CN123114425A_ABST
Patent Text Reader

Abstract

This invention discloses a BIM minimum unit data integration system, method, and apparatus based on model-data separation, belonging to the field of Building Information Modeling (BIM) data processing technology. The system processes the original BIM model, attribute data, and business data through model and data channels respectively, generating a lightweight model that retains association identifiers and standardized data records. The association engine establishes the association relationship between the minimum model unit and the standardized data records based on the unique component code and source component identifier. The model and data are stored separately and can be updated independently; after updates, they are re-associated through the association identifiers. This invention can reduce attribute loss and redundant processing during model conversion, and improve the association stability, integration efficiency, and traceability of multi-source engineering data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of building information modeling data processing technology, and in particular to a BIM minimum unit data integration system, method and apparatus based on data-model separation. Background Technology

[0002] With the widespread application of Building Information Modeling (BIM) technology in the engineering construction field, BIM models have become an important digital carrier in the engineering design, construction, and operation and maintenance phases. Around BIM models, a large amount of data associated with model components is typically generated, including multi-source heterogeneous business data such as design attribute data, construction quality data, engineering measurement data, schedule data, monitoring data, defect data, maintenance data, inspection data, and engineering documents.

[0003] Existing engineering digitization platforms typically require the conversion of original BIM models into lightweight models suitable for display on web pages, mobile devices, or digital twin platforms. This conversion process often involves format conversion, geometric optimization, model simplification, component splitting or merging, material optimization, and hierarchical detail conversion to improve model loading efficiency and display performance.

[0004] Typical BIM data integration methods usually involve directly writing model attributes into the BIM model and transferring it along with the entire model file. When using this method, adding or modifying attribute fields often requires returning to the original model for re-editing and re-exporting. Different software programs have varying levels of support for model entities, attribute sets, and custom fields, which may lead to attribute field omissions during format conversion or lightweight processing. Furthermore, the update frequency of geometric models and engineering business data differs, and storing both in the same model file can result in repeated model conversions and duplicate transfers of large files.

[0005] Throughout the entire lifecycle of a project, the same model component may correspond to multiple quality inspection records, measurement records, monitoring records, alarm records, defect records, maintenance records, and project documents. Data linking methods based on project-level or overall models are insufficient to meet the needs of component-level monitoring, defect tracking, and full-process traceability.

[0006] Furthermore, different modeling software and model conversion tools use different internal identifiers for components. After a model undergoes format conversion, component splitting, component merging, or re-export, the original component identifiers may change. When relying solely on component names, spatial locations, or internal identifiers of a single software for data attachment, it is difficult to stably restore the correspondence between model components and business data after a model update.

[0007] Therefore, a technical solution is needed that allows model geometric data, attribute data, and business data to be processed and updated independently, and that can continuously restore data relationships at the smallest model unit level. Summary of the Invention

[0008] To address the problems in existing technologies, such as the ease with which model component identifiers change after model lightweighting, difficulty in maintaining continuous association between the model and business data, the coupling between model updates and business data updates, and the difficulty in unified management of multi-source engineering data at the minimum model unit level, this invention provides a BIM minimum unit data integration system, method, and apparatus based on model-data separation. The technical solution is as follows: On the one hand, a BIM minimum unit data integration system based on digital model separation technology is provided, including a source data access module (110), an encoding module (120), a model processing module (130), a data processing module (140), an association engine (150), and a data storage module (170). The source data access module (110) is used to acquire the original BIM model and the attribute data and business data corresponding to the original BIM model; The encoding module (120) is used to establish the association identifier of the model component and establish the correspondence between the association identifier and the model component; The model processing module (130) is used to establish a model channel (202), perform model processing on the original BIM model, generate a lightweight model (204) composed of multiple minimum model units, and ensure that each minimum model unit retains at least one association identifier; The data processing module (140) is used to establish a data channel (205) that is independent of the model channel (202), process the attribute data and business data, generate standardized data records corresponding to each of the minimum model units, and form a minimum unit dataset (207). The association engine (150) is connected to the model processing module (130) and the data processing module (140) respectively, and is used to establish the association relationship between each of the smallest model units and the corresponding standardized data records based on the association identifier; The data storage module (170) is used to store the lightweight model (204), the minimum unit dataset (207), and the association relationship respectively, so that the lightweight model (204) and the minimum unit dataset (207) can be updated independently, and the association relationship can be re-established based on the updated association identifier.

[0009] Optionally, the association identifier includes a unique component code and a source component identifier; The encoding module (120) is used to generate a unique component code based on the model component information, obtain the source component identifier corresponding to the model component, and establish a mapping relationship between the unique component code and the source component identifier; The association engine (150) prioritizes establishing association relationships based on the unique component code. When the unique component code is missing or cannot form a unique association relationship, it restores the corresponding unique component code based on the source component identifier and establishes an association relationship.

[0010] Optionally, the unique component code includes an engineering object code, a function code, a component type code, and a location code; The encoding module (120) generates a unique component code based on the project object code, the function code, the component type code, and the positioning code; The encoding module (120) is also used to perform integrity verification, uniqueness verification and hierarchical consistency verification on the unique encoding of the component.

[0011] Optionally, the model processing module (130) establishes the model channel (202), including: Obtain the original BIM model (201); Perform model processing on the original BIM model (201); Generate a lightweight model that includes multiple minimum model units (204). Establish a model identifier index corresponding to each of the minimum model units; The model processing includes at least one of the following: format conversion, coordinate transformation, geometry optimization, lightweight processing, level of detail conversion, component merging, component splitting, material optimization, and rendering optimization. Furthermore, before or during the model processing, the association identifier is written into the model component so that the smallest model unit after model processing retains at least one association identifier.

[0012] Optionally, the data processing module (140) establishes the data channel (205), including: Obtain data from at least one model attribute source and at least one business data source; Perform structured and versioned processing on the acquired data (206); Generate corresponding standardized data records based on the associated identifier; Establish the minimum unit dataset (207) corresponding to the minimum model unit; in, The model attribute source includes at least one of the following: model attribute set, model attribute file, or model database; The business data source includes at least one of the following: business database, monitoring data source, document data source, message data source, or external data interface; The standardized data record includes at least the data record identifier, unique component code or source component identifier, data category, association cardinality, source system, generation time, validity period, data version, data content, and content checksum.

[0013] Optionally, the association engine (150) establishes an association between the smallest model unit in the lightweight model (204) and the standardized data record based on the unique component code and the source component identifier, including: Read the smallest model unit (301) in the lightweight model (204); Perform the first association matching (302) based on the unique component code; When a component's unique code corresponds to a unique standardized data record, a direct association is established (303). When the unique code of the component is missing or no unique matching result is formed, the mapping relationship is queried based on the source component identifier; When the source component identifier forms a unique matching result, the corresponding component unique code is restored, and a fallback association is established (304). When neither the unique component code nor the source component identifier forms a unique match, a candidate match is generated based on at least two of the following: geometric fingerprint, component type, spatial location, and parent path of the engineering decomposition structure. When the candidate match meets the preset confidence conditions, a candidate association relationship is established (305); otherwise, the corresponding record is written to the conflict queue and a manual confirmation result is received (306).

[0014] Optionally, it also includes an engineering decomposition structure management module (160) and a query and visualization module (180); the engineering decomposition structure management module (160) is used to establish an engineering decomposition structure catalog based on the unique component code, and to establish the correspondence between the engineering decomposition structure nodes and the smallest model unit; The engineering decomposition structure directory includes at least the engineering object level, the functional level, and the component level, and the component level node corresponds to the smallest model unit; The engineering decomposition structure management module (160) is used to bind design parameters, geometric information or basic component attributes to the corresponding component-level nodes in a one-to-one relationship, and bind quality inspection records, measurement records, monitoring records, alarm records, defect records, maintenance records or engineering documents to the corresponding component-level nodes in a one-to-many relationship; The query and visualization module (180) is used to respond to the selection operation of the minimum model unit, read the standardized data record corresponding to the minimum model unit, and respond to the selection operation of the standardized data record to reverse locate and highlight the corresponding minimum model unit. The query and visualization module (180) is also used to adjust the display attributes of the corresponding minimum model unit based on the monitoring alarm status, disease treatment status, or data integrity status.

[0015] Optionally, a consistency monitoring module (190) may also be included. The consistency monitoring module (190) is used to obtain model version M(n) (501), data version D(m) (502) and versioned associated ledger (503), and to perform identification and verification checks on model version M(n) (501), data version D(m) (502), association identifier and content verification (504). The versioned associated ledger (503) includes at least the associated record identifier, component unique code, source component identifier, data record identifier, model version, data version, matching basis, matching status, content checksum and validity period; When the lightweight model (204) is updated and the associated identifier remains consistent, the model version is updated and the original association relationship is maintained; When the standardized data record is updated and the associated identifier remains consistent, the corresponding standardized data record is written into the incremental update queue (505), the data version and content checksum are updated, and the lightweight model (204) remains unchanged; When the smallest model unit is split, merged, deleted, or its association identifier changes, the association engine (150) is invoked to re-establish the association relationship and retain the association relationship before the update. A consistent state (506) is generated based on the inspection and re-association results. The consistent state (506) includes at least one of direct association, fallback association, candidate association, conflict, and failure.

[0016] On the other hand, a BIM minimum unit data integration method based on digital model separation technology is provided, which is applied to a BIM minimum unit data integration system based on digital model separation technology, including: Obtain the original BIM model and its corresponding attribute and business data; Establish association identifiers for model components; Establish a model channel to process the original BIM model and generate a lightweight model composed of multiple minimum model units. Establish a data channel independent of the model channel to process the attribute data and business data and generate standardized data records; The association between the minimum model unit and the standardized data record is established based on the association identifier; The lightweight model, the standardized data records, and the association relationships are stored separately. After the lightweight model or the standardized data record is updated, the association relationship is re-established based on the updated association identifier.

[0017] On the other hand, a BIM minimum unit data integration device based on digital model separation technology is provided, including a processor (210), a memory (220), a model interface (230) and a data interface (240). The model interface (230), the data interface (240), and the memory (220) are respectively connected to the processor (210); The memory (220) stores a computer program; When the computer program is executed by the processor (210), the processor (210) executes the BIM minimum unit data integration method based on the digital-model separation technology; The data integration device (200) also includes a network interface (250) and a display / output interface (260). The network interface (250) is used to interact with external BIM platforms, CIM platforms or engineering management platforms; The display / output interface (260) is used to output lightweight models, standardized data records, correlation results, and engineering breakdown structure information.

[0018] Compared with the prior art, the present invention has the following significant advantages.

[0019] (1) The present invention adopts a data organization method of separating the model and the data, and establishes independent data processing channels for model data, attribute data and business data respectively, so that the lightweight model and standardized data records can be stored, maintained and updated independently. This avoids the problem in the prior art that the model and business data are highly coupled, which leads to the need to modify the business data synchronously when updating the model or to reprocess the model when updating the business data, thus improving the efficiency of engineering data management.

[0020] (2) By establishing model component association identifiers and establishing a mapping relationship between the unique component code and the source component identifier, the present invention enables the model to maintain a stable correspondence between the smallest model unit and the original model component after format conversion, lightweight processing, model splitting, model merging or version update, thereby improving the stability and reliability of the association relationship during the model conversion process.

[0021] (3) The present invention uses an association engine to establish the association relationship between the minimum model unit and the standardized data record based on the association identifier, realizing the unified organization of model geometric information and engineering business data at the minimum model unit level, enabling design data, construction data, quality data, monitoring data, maintenance data and other business data to be continuously integrated around the same minimum model unit, thereby improving the data management capability of the entire life cycle of the project.

[0022] (4) The present invention establishes a data processing mechanism in which the model channel and the data channel are independent of each other. When the model is updated, there is no need to update the business data synchronously. When the business data is added, modified or deleted, there is no need to regenerate the lightweight model. Data synchronization can be completed by simply re-establishing the association relationship based on the association identifier. This reduces the computational overhead caused by repeated model processing and repeated data maintenance and improves the system operating efficiency.

[0023] (5) By establishing the correspondence between the engineering decomposition structure nodes and the smallest model unit, the present invention enables engineering objects, functional nodes and component nodes to form a unified data organization structure, realize one-to-one, one-to-many or many-to-one association between model objects and multi-source business data, and improve the organization capability, query efficiency and sharing capability of engineering data.

[0024] (6) By setting up a consistency monitoring mechanism, the present invention continuously maintains the model version, data version and relationship, and automatically completes the relationship restoration and consistency maintenance after the model is updated or the business data is updated, thereby improving the integrity and traceability of the relationship between model data and business data and ensuring the continuity of data management throughout the entire life cycle of the project.

[0025] (7) The present invention uses the smallest model unit as the data association object. Compared with the method of using engineering projects, unit projects or overall models as data management objects, it can express the correspondence between model components and business data more precisely, improve the granularity of model data management, and provide a unified data foundation for model display, business query, status analysis and data sharing in engineering digital twin platform, smart construction site platform, smart operation and maintenance platform and urban information model platform. Attached Figure Description

[0026] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments of the present invention will be briefly described below.

[0027] Figure 1This is a schematic diagram of the overall structure of a BIM minimum unit data integration system based on data-model separation technology provided in an embodiment of the present invention; wherein, 100 is the data integration system, 101 is the BIM and business data source, 110 is the source data access module, 120 is the encoding module, 130 is the model processing module, 140 is the data processing module, 150 is the association engine, 160 is the engineering decomposition structure management module, 170 is the data storage module, 180 is the query and visualization module, and 190 is the consistency monitoring module.

[0028] Figure 2 This is a schematic diagram illustrating how the model channel and data channel of the present invention evolve independently and are re-converged through dual identifiers; wherein, 201 is the original BIM model, 202 is the model channel, 203 is the format conversion / lightweight processing, 204 is the lightweight model with the identifier field retained, 205 is the data channel, 206 is the structuring and versioning processing, and 207 is the smallest unit dataset.

[0029] Figure 3 This is a flowchart of the dual-identifier matching and anomaly rollback process of the present invention; wherein, 301 is reading the model unit identifier, 302 is judging the unique code of the component, 303 is establishing a direct association, 304 is judging the source component identifier matching, 305 is establishing a rollback association and completing the code, and 306 is conflict queue / manual confirmation.

[0030] Figure 4 This is a schematic diagram of the minimum unit hierarchy and multi-source data binding based on EBS in this invention; wherein, 401 is a bridge project-level node, 402 is a foundation and substructure functional-level node, 403 is a precast superstructure functional-level node, 404 is the minimum unit of bored pile, 405 is the minimum unit of pier column, 406 is the minimum unit of small box girder, and 407 is the minimum unit of support.

[0031] Figure 5 This is a schematic diagram of consistency maintenance for asynchronous updates of the model and data in this invention; where 501 is model version M(n), 502 is data version D(m), 503 is versioned associated ledger, 504 is identification and verification check, 505 is incremental update queue, and 506 is consistency state.

[0032] Figure 6 This is a schematic diagram of the data integration device structure provided in an embodiment of the present invention; wherein, 200 is the data integration device, 210 is the processor, 220 is the memory, 230 is the model interface, 240 is the data interface, 250 is the network interface, and 260 is the display / output interface. Detailed Implementation

[0033] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the following embodiments are for illustrative purposes only and are not intended to limit the scope of protection of the present invention. Various modifications, equivalent substitutions, or improvements made to the present invention by those skilled in the art without departing from the concept of the present invention should fall within the scope of protection of the present invention.

[0034] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0035] This embodiment provides a BIM minimum unit data integration system 100 based on digital-model separation technology, the overall structure of which is as follows: Figure 1 As shown, it includes a source data access module 110, an encoding module 120, a model processing module 130, a data processing module 140, an association engine 150, an engineering decomposition structure management module 160, a data storage module 170, a query and visualization module 180, and a consistency monitoring module 190.

[0036] like Figure 1 As shown, the BIM and business data source 101 is connected to the source data access module 110 and the encoding module 120, respectively. The source data access module 110 is connected to the model processing module 130, the encoding module 120 is connected to the data processing module 140, and the model processing module 130 and the data processing module 140 are connected to the association engine 150, respectively.

[0037] The association engine 150 is bidirectionally connected to the engineering breakdown structure management module 160 and to the query and visualization module 180; the engineering breakdown structure management module 160 is connected to the data storage module 170; the data storage module 170 is connected to the query and visualization module 180 and the consistency monitoring module 190 respectively, wherein the data storage module 170 and the consistency monitoring module 190 perform bidirectional data interaction.

[0038] The source data access module 110 registers the accessed model files, data files, database interfaces, and message interfaces, and generates a source identifier and import batch number for each import batch. The encoding module 120 reads the classification, functional system, and location information of the model components, generates a unique component code, and establishes a dual-identifier mapping record between the unique component code and the source component identifier.

[0039] The model processing module 130 forms a model channel 202 and outputs a lightweight model 204; the data processing module 140 forms a data channel 205 and outputs a minimum unit dataset 207. The association engine 150 receives the outputs from both channels and establishes the association relationship between the minimum model unit and the standardized data record based on the association identifier. The engineering decomposition structure management module 160 organizes the association results into an EBS hierarchical structure, and the data storage module 170 stores the lightweight model 204, the minimum unit dataset 207, the dual-identifier mapping record, the EBS directory tree, and the versioned association ledger 503, respectively.

[0040] The query and visualization module 180 is used to perform bidirectional queries and visual positioning between model units and standardized data records. The consistency monitoring module 190 is used to compare model versions, data versions, association identifiers, and content checksums, and trigger incremental updates or re-associations after model or data updates. These modules can be deployed on the same computing device, or they can be deployed using a distributed service or microservice approach.

[0041] Example 1 like Figure 2 As shown, this embodiment adopts a data processing method in which the model channel 202 and the data channel 205 are independent of each other, so as to realize the separate management of model geometric information and business data.

[0042] First, the source data access module 110 obtains the original BIM model 201. The original BIM model 201 can come from Revit, BentleyOpenBridge, Tekla, Civil3D, CATIA, or other software platforms that support BIM modeling, or it can come from open model files such as IFC.

[0043] In this embodiment, the smallest model unit is the smallest manageable physical object for the system to perform association, update, and query operations. For bridge engineering, small box girders, bored piles, pile caps, piers, supports, and expansion joints can all be used as component-level smallest model units; for steel bars, anchorages, or sensors that require part-level management, they can be further subdivided into part-level smallest model units. Subsequently, the encoding module 120 reads the model component information from the original BIM model 201 and establishes an association identifier for each model component. Preferably, the association identifier includes a unique component code and a source component identifier, wherein the unique component code is used to uniquely identify the model component in the engineering object, and the source component identifier is used to maintain the correspondence with the component identifier inside the original modeling software.

[0044] The coding module 120 generates a unique component code based on the engineering object to which the model component belongs, its functional classification, component type, and component location information. The unique component code can adopt a segmented coding structure formed by combining the engineering object code, function code, component type code, and location code in sequence.

[0045] The encoded fields are shown in the table below:

[0046] For example, a unique component code can be represented as "QL-001_XJ_ZK_A5-01", where "QL-001" represents the project object code, "XJ" represents the function code, "ZK" represents the component type code, and "A5-01" represents the location code. The coded fields can be separated by underscores, hyphens, or other delimiters. The specific coded characters and delimiters can be configured according to the project coding rules.

[0047] The source component ID is an internal identifier generated by the source BIM software for a model component. It can be a globally unique identifier, an element identifier, or an internal identifier from another source system. The unique component code is used to identify the same engineering component across software, phases, and business systems. The source component ID is used to preserve the original correspondence between the model component and the source BIM model.

[0048] Encoding module 120 establishes a dual-identity mapping record between the unique component code and the source component ID. The dual-identity mapping record includes at least: `source_system` is used to record the source system; `source_model_id` is used to record the source model identifier; `source_element_id` is used to record the source component ID; unique_code is used to record the unique code of a component; ebs_path is used to record the engineering decomposition structure path corresponding to the component; model_version is used to record the model version; geometry_fingerprint is used to record the geometric fingerprint of model components; active_flag is used to record the valid status of the mapping relationship.

[0049] Among them, unique_code is used for cross-stage business association; source_element_id is used to perform rollback positioning when the component's unique code is missing, damaged, or not retained after model conversion; ebs_path is used to determine the hierarchical position of the model component in the engineering decomposition structure directory; model_version is used to distinguish different model versions; geometry_fingerprint is used to generate candidate matches when neither the component's unique code nor the source component ID can achieve a unique match; and active_flag is used to indicate whether the current mapping record is valid.

[0050] In some implementations, the dual-identifier mapping record may also include at least one of the following: mapping record identifier, source data batch, component type, spatial location, creation time, update time, creator, verification status, and historical version identifier.

[0051] The encoding module 120 can also perform integrity and consistency checks on the dual-identifier mapping records. The integrity check is used to check whether necessary fields such as the component unique code, source component ID, source model identifier, and model version are missing; the consistency check is used to check whether the same component unique code corresponds to multiple valid source component IDs, whether the same source component ID corresponds to multiple valid component unique codes, and whether the component unique code is consistent with the EBS path.

[0052] When duplicate mapping, invalid mapping, or hierarchical conflict is detected, the encoding module 120 generates a mapping exception record and sends the mapping exception record to the association engine 150 or the exception handling queue 306 to avoid incorrect association.

[0053] After the association identifier is established, the original BIM model 201 enters the model channel 202.

[0054] The model processing module 130 performs model processing 203 on the original BIM model 201 within the model channel 202. Model processing 203 may include one or more processing methods such as format conversion, coordinate transformation, geometry optimization, lightweight processing, hierarchical detail conversion, component splitting, component merging, material optimization, and rendering optimization.

[0055] During the model processing, the model processing module 130 keeps the associated identifiers of each model component unchanged and establishes the correspondence between the smallest model unit and the associated identifier in the lightweight model 204.

[0056] The model processing module 130 can convert the original BIM model 201 into 3D Tiles, FBX, glTF, or other intermediate formats that the application platform can read. Before model processing, the unique component code and source component identifier can be written into the model unit name field, custom attribute field, extended attribute set, or bypass index file. After model processing, the model processing module 130 reads the corresponding fields or bypass index file, establishes the model identifier index of the lightweight model 204, and checks whether each smallest model unit retains at least one associated identifier. The lightweight model 204 is generated after model processing.

[0057] Data channel 205 operates synchronously with model processing.

[0058] The data processing module 140 acquires attribute data and business data, and performs structured processing and versioning processing on the acquired data 206.

[0059] The structured processing includes field mapping, data type conversion, unit unification, time format unification, and data integrity verification; the versioning processing includes data version numbering, update time recording, and data status identification.

[0060] After processing, the data processing module 140 generates standardized data records and further establishes a minimum unit dataset 207. The standardized data records include at least a data record identifier, a unique component code or source component identifier, data category, association cardinality, lifecycle stage, source system, generation time, validity period, data version, data content, and content checksum. Attribute data and business data can originate from IFC attribute sets, attribute tables exported from BIM software, business databases, monitoring message flows, document directories, or external business interfaces.

[0061] Therefore, throughout the entire process, the lightweight model 204 and the minimum unit dataset 207 are always stored and maintained separately. The two are only associated through an association identifier, and business data is no longer directly written into the model file, thereby achieving decoupled management of model data and business data.

[0062] When the model is updated, only the lightweight model 204 needs to be regenerated; when the business data is updated, only the smallest unit dataset 207 needs to be updated, without having to reprocess another part of the data, thereby improving the data processing efficiency of the entire system.

[0063] Example 2 like Figure 3 As shown, the association engine 150 reads a minimum model unit in the lightweight model 204 and reads the association identifier (301) retained by the minimum model unit.

[0064] The association engine 150 first determines whether the component's unique code can form a unique match (302). When the component's unique code exists and corresponds to a unique standardized data record within the current project object scope, a direct association is established (303).

[0065] When a component's unique code is missing or no unique match is formed, the association engine 150 determines whether the source component identifier can form a unique match (304). When the source component identifier can uniquely locate the dual identifier mapping record, the corresponding component's unique code is restored, a rollback association is established, and the code is completed (305).

[0066] When neither the unique component code nor the source component identifier can form a unique match, the association engine 150 generates candidate matches based on at least two of the following: component type, spatial location, geometric fingerprint, and EBS context. The geometric fingerprint can be generated based on the bounding box size, centroid coordinates, volume, surface area, and topological adjacency summary of the smallest model unit; the EBS context may include parent functional nodes, location segments, and adjacent components.

[0067] Candidate confidence can be expressed as: S=w1Itype+w2Iposition+w3Igeometry+w4Iparent, Where Itype, Iposition, Igeometry, and Iparent represent the normalized similarity of component type, spatial position, geometric fingerprint, and parent path, respectively, and w1 to w4 are the corresponding weights, and the sum of w1 to w4 is 1.

[0068] When the confidence level of the highest candidate reaches the first threshold and the difference between the confidence level of the highest candidate and the confidence level of the second highest candidate reaches the second threshold, a candidate association is established; otherwise, the corresponding record is written to the conflict queue and the manual confirmation result 306 is received.

[0069] After each match is completed, the association engine 150 writes the matching result to the versioned association ledger 503. The versioned association ledger 503 records at least the relation_id, unique_code, source_element_id, data_record_id, model_version, data_version, match_basis, match_status, checksum, and valid_time to support the tracing and rollback of association relationships.

[0070] Example 3 like Figure 4 As shown, in this embodiment, the engineering breakdown structure management module 160 is used to establish an engineering breakdown structure directory and organize standardized data records into the corresponding smallest model unit.

[0071] After the Engineering Breakdown Structure Management Module 160 establishes the Engineering Breakdown Structure directory, it links standardized data records to each EBS node according to their corresponding relationships.

[0072] Preferably, the EBS directory consists of project object level, function level, and component level, where component level nodes correspond to the smallest model unit. The system can also be configured to create part level nodes according to project management needs. When a component consists of multiple parts, the coding module 120 parses the hierarchical information in the component's unique code, automatically creates the missing parent node, and attaches the corresponding component node to the corresponding EBS path.

[0073] Standardized data records are attached to the corresponding EBS nodes according to the business type.

[0074] Preferably, the data organization methods for different stages are shown in the table below.

[0075]

[0076] The data generated during the design phase mainly corresponds to the geometric information of the model; the data generated during the construction and operation and maintenance phases continue to increase as the project runs, so a minimum model unit can be associated with multiple construction records or operation and maintenance records.

[0077] To support unified management of data throughout the entire project lifecycle, this embodiment adopts a standardized recording method to organize business data.

[0078] Taking monitoring point data as an example, standardized data records can include monitoring point identification code, monitoring point name, unique component code, component name, monitoring index, unit, equipment name, most recent monitoring value, acquisition time, monitoring location, and elevation. Structural monitoring points are bound to the smallest model unit at the component level; when environmental monitoring points cannot be bound to specific components, they can be bound to engineering object-level nodes or functional-level nodes.

[0079] The above standardized records all establish the association between the component's unique code and the smallest model unit.

[0080] For data that can be directly located to model components, the Engineering Decomposition Structure Management Module 160 will directly attach standardized records to the corresponding component-level nodes.

[0081] For data that cannot be located to specific model components, such as environmental monitoring data, regional monitoring data, or comprehensive statistical data, it is linked according to the engineering object or functional node, so that the corresponding data can be managed uniformly at the engineering object level or functional level.

[0082] Taking disease management as an example, disease records are stored in a standardized manner.

[0083] Taking disease data as an example, standardized data records can include disease identification code, disease number, unique component code, reporting date, disease type, disease description, data source, disease photos, and treatment status. When querying a specific component, the system returns all disease records associated with that component and corresponding maintenance records; when querying a parent EBS node, the system aggregates the number of diseases and treatment status of its descendant components, and can display them in the lightweight model 204 with different display attributes through the query and visualization module 180.

[0084] When a user queries a component, the query and visualization module 180 locates the corresponding smallest model unit based on the component's unique code and returns all disease records associated with that component.

[0085] When a user queries a project object node or a functional node, the system uses the EBS catalog to count the number of defects, the types of defects, and the status of defect treatment within the corresponding range, and returns the statistical results to the query and visualization module 180 for visualization display.

[0086] like Figure 4 As shown, bridge project-level node 401 includes foundation and substructure functional node 402 and precast superstructure functional node 403. Foundation and substructure functional node 402 includes bored pile minimum unit 404 and pier minimum unit 405; precast superstructure functional node 403 includes small box girder minimum unit 406 and bearing minimum unit 407.

[0087] Figure 4 The hierarchy shown is an example of a bridge engineering project. The Engineering Decomposition Structure Management module 160 can automatically create missing parent-level nodes based on the segmentation information in the unique component code, and attach the component-level minimum model unit to the corresponding EBS path. The system can also expand the part-level nodes according to project management requirements.

[0088] Design parameters, geometric information, and basic component properties can be associated one-to-one with the smallest model unit; quality inspection records, measurement records, monitoring points, monitoring alarms, disease records, maintenance records, design drawings, test reports, and on-site photos can be associated one-to-many with the smallest model unit.

[0089] When any EBS node is queried, the Engineering Decomposition Structure Management Module 160 returns the smallest model unit and standardized data record associated with that node and all its descendant nodes, and aggregates and generates the number of components, data integrity, monitoring status, number of defects or treatment status.

[0090] The query and visualization module 180 responds to the selection operation of the smallest model unit, reads all standardized data records corresponding to the smallest model unit according to the association relationship; responds to the selection operation of standardized data records, reverses the location and highlights the corresponding smallest model unit.

[0091] The query and visualization module 180 responds to the selection operation of the smallest model unit, reads all standardized data records corresponding to the smallest model unit according to the association relationship, and outputs at least one of the following: design parameters, quality inspection records, measurement records, monitoring records, disease records, maintenance records, and engineering documents.

[0092] The query and visualization module 180 also responds to the selection operation of the standardized data record, and reverses the location and highlights the corresponding smallest model unit based on the component unique code or source component identifier carried by the standardized data record.

[0093] The query and visualization module 180 can adjust the display attributes of the corresponding smallest model unit according to the monitoring alarm status, disease treatment status, quality inspection status, or data integrity status. The display attributes include at least one of color, transparency, outline, blinking status, and visibility status.

[0094] Example 4 like Figure 5 As shown, model version M(n) 501 and data version D(m) 502 are respectively input into the versioned associated ledger 503. The consistency monitoring module 190 performs identification and checksum checks 504 based on the versioned associated ledger 503, and forms an incremental update queue 505 and a consistency state 506 according to the check results.

[0095] When only the content of the standardized data record changes, and the unique component code or source component identifier remains unchanged, only the data version and content checksum are updated, and the corresponding data record is written to the incremental update queue 505, without triggering the re-conversion of the original BIM model 201.

[0096] When only the geometry of lightweight model 204 changes and the association identifier remains unchanged, update model version M(n) 501 and model identifier index, and restore the original association relationship according to the versioned association ledger 503.

[0097] When the smallest model unit is split, merged, deleted, or the association identifier changes, the association engine 150 re-executes direct matching, fallback matching, or candidate matching, and marks the association relationship as direct association, fallback association, candidate association, conflict, or invalid.

[0098] For relationships that have changed, the versioned relationship ledger 503 retains the relationship records before the update, as well as the model version, data version, matching basis, matching status, matching time, and validity period, to support historical tracing and relationship rollback.

[0099] In a precast small box girder viaduct project, the source BIM model was built at the component level. The unique component code of a certain small box girder is "QL-ZXGJ_SY_XX_L1-2", where "QL-ZXGJ" represents the main elevated unit project, "SY" represents the precast superstructure, "XX" represents the small box girder, and "L1-2" represents the second segment of the first span.

[0100] The system exports an attribute table, including source component identifiers and unique component codes, from the source model and converts the original model into a lightweight model 204. Data channel 205 converts design attributes, quality inspection data, and measurement records into standardized data records. The association engine 150 prioritizes matching the corresponding smallest model unit using "QL-ZXGJ_SY_XX_L1-2"; when only the source component identifier is retained after model processing, the unique component code is recovered through a dual-identifier mapping record, and a fallback association is established.

[0101] When a user selects the smallest model unit of the small box girder, the query and visualization module 180 reads and displays its design, quality inspection and measurement records; when new disease records, monitoring records or maintenance records are added later, only the smallest unit dataset 207 is updated, and there is no need to regenerate the lightweight model 204.

[0102] Example 5 like Figure 6 As shown, this embodiment provides a data integration device 200 for implementing the above-described data integration system.

[0103] The data integration device 200 includes a processor 210, a memory 220, a model interface 230, a data interface 240, a network interface 250, and a display / output interface 260.

[0104] The processor 210 is used to execute the computer program in the memory 220 to implement the data integration method of the present invention.

[0105] The memory 220 is used to store data such as computer programs, lightweight models 204, minimum unit datasets 207, versioned associated ledgers 503, and project breakdown structure directories.

[0106] The model interface 230 is used to receive the original BIM model 201 and output the lightweight model 204 generated by the model processing module 130.

[0107] Data interface 240 is used to receive attribute data and business data, and send the acquired data to data processing module 140 for structured processing and versioning processing.

[0108] Network interface 250 is used to communicate with BIM platform, CIM platform, project management platform, smart construction site platform, smart operation and maintenance platform or other external information systems to realize the sharing and exchange of model data, business data and related data.

[0109] The display / output interface 260 is used to output the lightweight model 204, the minimum unit dataset 207, the engineering decomposition structure directory, and related results, providing users with functions such as model browsing, data querying, business display, and correlation analysis.

[0110] When processor 210 calls a computer program stored in memory 220, it performs the following processing: Obtain the original BIM model 201 through model interface 230; Establish association identifiers for model components; Establish model channel 202 and data channel 205 separately to process model data and business data independently; Establish the association between the smallest model unit and standardized data records based on the association identifier; Store lightweight model 204, minimum unit dataset 207, and related relationships respectively; After the model data or business data is updated, the association relationship is re-established based on the updated association identifier, and the consistency status 506 is updated.

[0111] Therefore, the data integration device 200 of this embodiment can realize all the functions of the data integration system and data integration method of the above embodiments, and will not be described again here.

[0112] This invention does not limit specific project types, BIM software, model formats, or database types. The smallest model unit can be applied to bridges, roads, tunnels, buildings, rail transit, and municipal pipelines; the unique component code can use letters, numbers, or a combination of both; standardized data records can be stored in relational databases, document databases, graph databases, or object storage; the versioned associated ledger 503 can be implemented using relational tables, event logs, or distributed ledgers.

[0113] The data integration device 200 can be a server, workstation, edge computing gateway, or a cluster of multiple computing devices. The memory 220 can include volatile and non-volatile memory. The functional modules can be executed by the same processor or distributed across multiple computing nodes.

[0114] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0115] Those skilled in the art will understand that all or part of the processing in the above method embodiments can be implemented in hardware, or in hardware related to computer program instructions. The computer program can be stored in a computer-readable storage medium, which may include a read-only memory, random access memory, a magnetic disk, an optical disk, or other media capable of storing program instructions. The above embodiments are for illustrative purposes only and are not intended to limit the scope of protection of the present invention; any modifications, equivalent substitutions, or improvements made within the scope of the present invention should fall within the protection scope of the present invention.

Claims

1. A BIM minimum unit data integration system based on digital-analog separation technology, characterized in that, It includes a source data access module (110), an encoding module (120), a model processing module (130), a data processing module (140), an association engine (150), and a data storage module (170). The source data access module (110) is used to acquire the original BIM model and the attribute data and business data corresponding to the original BIM model; The encoding module (120) is used to establish the association identifier of the model component and establish the correspondence between the association identifier and the model component; The model processing module (130) is used to establish a model channel (202), perform model processing on the original BIM model, generate a lightweight model (204) composed of multiple minimum model units, and ensure that each minimum model unit retains at least one association identifier; The data processing module (140) is used to establish a data channel (205) that is independent of the model channel (202), process the attribute data and business data, generate standardized data records corresponding to each of the minimum model units, and form a minimum unit dataset (207). The association engine (150) is connected to the model processing module (130) and the data processing module (140) respectively, and is used to establish the association relationship between each of the smallest model units and the corresponding standardized data records based on the association identifier; The data storage module (170) is used to store the lightweight model (204), the minimum unit dataset (207), and the association relationship respectively, so that the lightweight model (204) and the minimum unit dataset (207) can be updated independently, and the association relationship can be re-established based on the updated association identifier.

2. The BIM minimum unit data integration system based on digital-model separation technology according to claim 1, characterized in that, The association identifier includes a unique component code and a source component identifier; The encoding module (120) is used to generate a unique component code based on the model component information, obtain the source component identifier corresponding to the model component, and establish a mapping relationship between the unique component code and the source component identifier; The association engine (150) prioritizes establishing association relationships based on the unique component code. When the unique component code is missing or cannot form a unique association relationship, it restores the corresponding unique component code based on the source component identifier and establishes an association relationship.

3. The BIM minimum unit data integration system based on digital-model separation technology according to claim 2, characterized in that, The unique component code includes the project object code, function code, component type code, and location code; The encoding module (120) generates a unique component code based on the project object code, the function code, the component type code, and the positioning code; The encoding module (120) is also used to perform integrity verification, uniqueness verification and hierarchical consistency verification on the unique encoding of the component.

4. The BIM minimal unit dataset integration system based on digital-analog separation technology according to claim 1, characterized in that, The model processing module (130) establishes the model channel (202), including: Obtain the original BIM model (201); Perform model processing on the original BIM model (201); Generate a lightweight model that includes multiple minimum model units (204). Establish a model identifier index corresponding to each of the minimum model units; The model processing includes at least one of the following: format conversion, coordinate transformation, geometry optimization, lightweight processing, level of detail conversion, component merging, component splitting, material optimization, and rendering optimization. Furthermore, before or during the model processing, the association identifier is written into the model component so that the smallest model unit after model processing retains at least one association identifier.

5. The BIM minimum unit data integration system based on digital-model separation technology according to claim 1 or 4, characterized in that, The data processing module (140) establishes the data channel (205), including: Obtain data from at least one model attribute source and at least one business data source; Perform structured and versioned processing on the acquired data (206); Generate corresponding standardized data records based on the associated identifier; Establish the minimum unit dataset (207) corresponding to the minimum model unit; in, The model attribute source includes at least one of the following: model attribute set, model attribute file, or model database; The business data source includes at least one of the following: business database, monitoring data source, document data source, message data source, or external data interface; The standardized data record includes at least the data record identifier, unique component code or source component identifier, data category, association cardinality, source system, generation time, validity period, data version, data content, and content checksum.

6. The BIM minimum unit data integration system based on digital-model separation technology according to claim 2, characterized in that, The association engine (150) establishes the association relationship between the smallest model unit in the lightweight model (204) and the standardized data record based on the unique component code and the source component identifier, including: Read the smallest model unit (301) in the lightweight model (204); Perform the first association matching (302) based on the unique component code; When a component's unique code corresponds to a unique standardized data record, a direct association is established (303). When the unique code of the component is missing or no unique matching result is formed, the mapping relationship is queried based on the source component identifier; When the source component identifier forms a unique matching result, the corresponding component unique code is restored, and a fallback association is established (304). When neither the unique component code nor the source component identifier forms a unique match, a candidate match is generated based on at least two of the following: geometric fingerprint, component type, spatial location, and parent path of the engineering decomposition structure. When the candidate match meets the preset confidence conditions, a candidate association relationship is established (305); otherwise, the corresponding record is written to the conflict queue and a manual confirmation result is received (306).

7. The BIM minimal cell dataset integration system based on digital-analog separation technology according to claim 6, wherein, It also includes an engineering breakdown structure management module (160) and a query and visualization module (180). The engineering decomposition structure management module (160) is used to establish an engineering decomposition structure catalog based on the unique component code, and to establish the correspondence between the engineering decomposition structure nodes and the smallest model unit; The engineering decomposition structure directory includes at least the engineering object level, the functional level, and the component level, and the component level node corresponds to the smallest model unit; The engineering decomposition structure management module (160) is used to bind design parameters, geometric information or basic component attributes to the corresponding component-level nodes in a one-to-one relationship, and bind quality inspection records, measurement records, monitoring records, alarm records, defect records, maintenance records or engineering documents to the corresponding component-level nodes in a one-to-many relationship; The query and visualization module (180) is used to respond to the selection operation of the minimum model unit, read the standardized data record corresponding to the minimum model unit, and respond to the selection operation of the standardized data record to reverse locate and highlight the corresponding minimum model unit. The query and visualization module (180) is also used to adjust the display attributes of the corresponding minimum model unit based on the monitoring alarm status, disease treatment status, or data integrity status.

8. The BIM minimal unit dataset integration system based on digital-analog separation technology according to claim 1, wherein, It also includes a consistency monitoring module (190); The consistency monitoring module (190) is used to obtain model version M(n) (501), data version D(m) (502) and versioned associated ledger (503), and to perform identification and verification checks on model version M(n) (501), data version D(m) (502), association identifier and content verification (504). The versioned associated ledger (503) includes at least the associated record identifier, component unique code, source component identifier, data record identifier, model version, data version, matching basis, matching status, content checksum and validity period; When the lightweight model (204) is updated and the associated identifier remains consistent, the model version is updated and the original association relationship is maintained; When the standardized data record is updated and the associated identifier remains consistent, the corresponding standardized data record is written into the incremental update queue (505), the data version and content checksum are updated, and the lightweight model (204) remains unchanged; When the smallest model unit is split, merged, deleted, or its association identifier changes, the association engine (150) is invoked to re-establish the association relationship and retain the association relationship before the update. A consistent state (506) is generated based on the inspection and re-association results. The consistent state (506) includes at least one of direct association, fallback association, candidate association, conflict, and failure.

9. A BIM minimum unit data integration method based on digital-analog separation technology, characterized in that, The BIM minimum unit data integration system based on digital-model separation technology as described in any one of claims 1 to 8 includes: Obtain the original BIM model and its corresponding attribute and business data; Establish association identifiers for model components; Establish a model channel to process the original BIM model and generate a lightweight model composed of multiple minimum model units. Establish a data channel independent of the model channel to process the attribute data and business data and generate standardized data records; The association between the minimum model unit and the standardized data record is established based on the association identifier; The lightweight model, the standardized data records, and the association relationships are stored separately. After the lightweight model or the standardized data record is updated, the association relationship is re-established based on the updated association identifier.

10. A BIM minimum unit data integration apparatus based on digital-analog separation technology, characterized by, It includes a processor (210), a memory (220), a model interface (230), and a data interface (240). The model interface (230), the data interface (240), and the memory (220) are respectively connected to the processor (210); The memory (220) stores a computer program; When the computer program is executed by the processor (210), the processor (210) performs the method of claim 9; The data integration device (200) also includes a network interface (250) and a display / output interface (260). The network interface (250) is used to interact with external BIM platforms, CIM platforms or engineering management platforms; The display / output interface (260) is used to output lightweight models, standardized data records, correlation results, and engineering breakdown structure information.