A BIM model full life cycle splitting and cross-model synchronization method and system

Abstract

This disclosure proposes a method and system for BIM model full lifecycle decomposition and cross-model synchronization. The method includes: encoding BIM model components based on full lifecycle coding rules, binding private attributes of each engineering stage with the component codes of that stage, storing them in the component extended attributes, and generating a BIM master model containing multi-stage attribute information; setting BIM model decomposition rules based on a rule engine; parsing the code of each component in the BIM model, comparing the code with the filtering conditions in the decomposition rules according to hierarchy, packaging the component data corresponding to the successfully matching codes, and saving them as sub-models; establishing association mappings between models; when the source model is modified, the synchronization engine executes the synchronous update of the target model according to the association mapping between the source model and its associated target model, thereby improving the efficiency of cross-stage multi-participant collaboration and providing solid technical support for the digital transformation of the construction industry.

Description

Technical Field

[0001] This disclosure relates to the field of engineering digital applications, specifically to a method and system for the full lifecycle decomposition and cross-model synchronization of BIM models. Background Technology

[0002] Driven by the digital wave, Building Information Modeling (BIM) technology, with its unique advantages of 3D visualization and information integration, has rapidly gained popularity in the construction industry, permeating the entire lifecycle of building design, construction, and operation and maintenance. In the design phase, BIM technology can be used for scheme simulation and clash detection, effectively avoiding design conflicts, reducing engineering changes, and significantly improving design quality and efficiency. During construction, relying on BIM models for construction detailing, process simulation, and on-site management enables refined control of the construction process, improving construction efficiency and safety. In the operation and maintenance phase, BIM models, as the core carrier of facility information, provide reliable data support for equipment monitoring, maintenance management, and space operation, helping to extend the building's lifespan.

[0003] However, the accuracy and requirements for the model vary at each stage, from design to construction to operation and maintenance. Refining and perfecting information within a single model is inefficient, and the continuous updates and iterations of the model throughout the project make model management and use even more complex.

[0004] To improve model efficiency, the overall model is typically broken down into smaller, more manageable sub-models. Common decomposition methods include manual component selection and using modeling software to divide the model according to static rules such as profession or floor level. However, both methods have significant shortcomings. Firstly, the decomposition process lacks in-depth consideration of business logic, resulting in a lack of effective correlation between the decomposed models and the original models. Modifications to the decomposed models cannot be synchronized back to the original models, creating "data silos." Secondly, the decomposition rules are rigid and difficult to adapt to the dynamic needs of different stages and stakeholders for model data, easily leading to component data redundancy or omissions, affecting data integrity and consistency.

[0005] To address the prominent issues in traditional BIM model applications, an innovative BIM management method is urgently needed. This method should support full lifecycle management based on project phases, functions, and other dimensions, while also enabling intelligent multi-dimensional model decomposition. This innovative approach allows for on-demand extraction, dynamic association, and synchronous updates of model data, thereby breaking down data silos, reducing repetitive work, mitigating data error risks, and improving cross-phase, multi-participant collaboration efficiency, thus providing solid technical support for the digital transformation of the construction industry. Summary of the Invention

[0006] This disclosure provides a method and system for the full lifecycle decomposition and cross-model synchronization of BIM models, which can realize the on-demand extraction, dynamic association and synchronous update of model data, improve the collaboration efficiency of multiple participants across stages, and provide solid technical support for the digital transformation of the construction industry.

[0007] Firstly, this disclosure provides a method for the full lifecycle decomposition and cross-model synchronization of BIM models, including the following steps:

[0008] S1: Encode BIM model components based on the full lifecycle coding rules, bind the private attributes of each engineering stage with the component code of that engineering stage, store them in the component extended attributes, and generate a BIM master model containing multi-stage attribute information;

[0009] The coding structure consists of engineering stage, functional classification, spatial dimension, component type, and component number;

[0010] S2: Set BIM model splitting rules based on the rule engine. The filtering conditions in the splitting rules should include at least one or more of the following dimensions: project stage, functional classification, spatial location, component type and component number.

[0011] S3: Parse the code of each component in the BIM model, compare the code with the filtering conditions in the splitting rules according to the level, package the component data corresponding to the successfully matched code, and save it as a sub-model;

[0012] S4: By combining "metadata-driven + graph database", establish the association mapping between sub-models and the main model, and between sub-models;

[0013] S5: When the source model is modified, a synchronization operation command is automatically triggered and transmitted to the synchronization engine. The synchronization engine performs the synchronization update of the target model according to the association mapping between the source model and its associated target model.

[0014] The source model is either the main model or a sub-model, and the target model is either the main model or a sub-model.

[0015] In some embodiments, step S1 includes the following steps:

[0016] S101: Read BIM model data, including component tree hierarchy, component function, component type, spatial location and other attachment attributes;

[0017] S102: Based on the full life cycle coding rules and BIM model data, automatically generate component codes. The coding structure consists of engineering stage, functional classification, spatial location, component type and component serial number.

[0018] S103: Bind the private attributes of each engineering stage to the component code of that engineering stage and store them in the extended attributes of the component. At the same time, associate the public attributes of the component to finally generate a BIM master model containing multi-stage attribute information.

[0019] In some embodiments, step S3 specifically includes:

[0020] The code of each component in the BIM model is parsed, and the code is compared with the filtering conditions in the splitting rules according to the hierarchy. All successfully matched component codes are marked, the private attributes of the corresponding stage are automatically retrieved, and the basic public attributes of the component are associated to form complete component data. Finally, the filtered component data is packaged to generate independent sub-models.

[0021] In some embodiments, in step S4, the relationship between the main model and the sub-model is hierarchical, and the relationship between the sub-models includes unidirectional dependency and bidirectional non-hierarchical relationship.

[0022] In some embodiments, step S4 specifically includes the following steps:

[0023] S401 defines the association mapping between the main model and the sub-model, and between the sub-models through metadata, including the association relationship between the main model and the sub-model, the data mapping relationship, and the update rules.

[0024] S402 is a graph database built based on metadata, which stores the relationships between sub-models and the main model, as well as between sub-models.

[0025] In some embodiments, step S5 includes the following steps:

[0026] S501: When the source model is modified, the system automatically triggers a synchronization operation command and transmits it to the synchronization engine.

[0027] S502, the synchronization engine queries the graph database to obtain all target models associated with the source model; for each target model, the synchronization engine further queries the metadata of that target model;

[0028] S503, the synchronization engine, performs synchronous updates to the target model based on the data mapping relationships and update rules defined in the metadata.

[0029] In some embodiments, in step S5, the system maintains a global version record table to record the current valid version number of the main model and each sub-model, performs conflict detection through an optimistic locking mechanism, and combines a conflict handling process to ensure data consistency.

[0030] Secondly, this disclosure provides a BIM model lifecycle decomposition and cross-model synchronization system for executing the aforementioned BIM model lifecycle decomposition and cross-model synchronization method, the system comprising:

[0031] The main model construction module is used to encode BIM model components based on the full life cycle coding rules, bind the private attributes of each engineering stage with the component code of that engineering stage, store them in the component extended attributes, and generate a BIM main model containing multi-stage attribute information.

[0032] The coding structure consists of engineering stage, functional classification, spatial dimension, component type, and component number;

[0033] The splitting rule setting module is used to set BIM model splitting rules based on the rule engine. The filtering conditions in the splitting rules must include at least one or more of the following dimensions: project stage, functional classification, spatial location, component type and component number.

[0034] The sub-model splitting module is used to parse the code of each component in the BIM model, compare the code with the filtering conditions in the splitting rules according to the level, and package the component data corresponding to the successfully matched code into a sub-model.

[0035] The model association establishment module is used to establish association mappings between sub-models and the main model, and between sub-models themselves, through a combination of "metadata-driven + graph database".

[0036] The synchronization update module is used to automatically trigger a synchronization operation command and send it to the synchronization engine when the source model is modified. The synchronization engine then performs a synchronization update of the target model based on the association mapping between the source model and its associated target model.

[0037] The source model is either the main model or a sub-model, and the target model is either the main model or a sub-model.

[0038] The beneficial effects of this disclosure are that, compared with the prior art, this disclosure has the following advantages:

[0039] 1. In this disclosed solution, BIM model components are coded based on the full lifecycle coding rules. Each component includes public attributes and stage-specific private attributes. The private attributes of each engineering stage are bound to the component code of that engineering stage and stored in the component extended attributes to generate a BIM master model containing multi-stage attribute information.

[0040] By constructing a full lifecycle coding system, unique codes are bound to different engineering stages of components. By recognizing the codes, sub-models can be automatically split according to dimensions such as stage, function, or space, which greatly simplifies the query, update, and scenario-based application process of BIM models in cross-stage collaboration.

[0041] 2. The sub-model and the main model are combined through "metadata-driven + graph database" to establish the association mapping between the main model and the sub-model, and between the sub-models. During the model update process, only the main model or the sub-model needs to be operated on, and the synchronization engine will automatically complete the synchronous update of the associated models, breaking the "island" state, reducing duplication of work, reducing the risk of data errors, and improving the efficiency of cross-stage multi-participant collaboration.

[0042] 3. In this disclosed solution, when a sub-model is modified, it is not necessary to go through the main model. The sub-model can directly interact and synchronize to achieve synchronous updates between sub-models (for example, bidirectional data synchronization can be achieved between the design sub-model and the construction sub-model). This effectively reduces the data synchronization delay between models, thereby ensuring that data synchronization can be carried out efficiently and stably in large-scale component scenarios. Attached Figure Description

[0043] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0044] Figure 1 A schematic diagram illustrating a method for the full lifecycle splitting and cross-model synchronization of a BIM model provided in this embodiment of the disclosure;

[0045] Figure 2 A schematic diagram illustrating another method for BIM model lifecycle splitting and cross-model synchronization provided in this embodiment of the disclosure;

[0046] Figure 3 This is a schematic diagram of a BIM model lifecycle splitting and cross-model synchronization system provided in an embodiment of this disclosure.

[0047] The accompanying drawings have illustrated specific embodiments of this disclosure, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this disclosure to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0048] The present disclosure will be further described below with reference to the accompanying drawings. The following embodiments are only used to illustrate the technical solutions of the present disclosure more clearly, and should not be used to limit the scope of protection of the present disclosure.

[0049] like Figure 1 As shown, the first embodiment of this disclosure proposes a method for the full lifecycle decomposition and cross-model synchronization of a BIM model, including:

[0050] S1: Encode BIM model components based on the full lifecycle coding rules, bind the private attributes of each engineering stage with the component code of that engineering stage, store them in the component extended attributes, and generate a BIM master model containing multi-stage attribute information.

[0051] The coding structure consists of engineering stage, functional classification, spatial dimension, component type and component number.

[0052] like Figure 2 As shown, in one optional implementation, step S1 includes:

[0053] S101: Read BIM model data, including component tree hierarchy, component function, component type, spatial location and other attachment attributes;

[0054] S102: Based on the full life cycle coding rules and BIM model data, automatically generate component codes. The coding structure consists of engineering stage, functional classification, spatial location, component type and component serial number.

[0055] The full lifecycle coding rules adopt a multi-dimensional combined architecture, covering multiple dimensions such as engineering stage (design, construction, operation and maintenance), functional classification (foundation, abutment, pier, electromechanical, etc.), spatial location (section, area), component type (pier cap, column), and component serial number. Among them, the coding rules are unique and scalable, and can adapt to different needs and changes in projects.

[0056] Project Phase Dimensions: Based on the entire project lifecycle, projects are divided into design, construction, and operation / maintenance phases. In the coding rules, each phase dimension is represented by a letter, such as "D" for design, "C" for construction, and "O" for operation / maintenance. Each component phase has three phase dimensions, and the coding changes as different phases are switched.

[0057] Functional Classification Dimension: Based on the functional classification of the project, the project is divided into basic functions, abutment functions, and pier functions, etc. In the coding rules, functional classification is represented by letters, such as "JC" for basic functions, "QT" for abutment functions, and "QD" for pier functions.

[0058] Spatial location dimension: Based on the spatial distribution of the project, the project is divided into different sections, areas, etc. In the coding rules, spatial location is represented by numbers, such as "1" for section 1, "2" for section 2, "A" for area A, and "B" for area B.

[0059] Component Type Dimension: Components are categorized according to their type within the project. In the coding rules, component types are represented by letters, such as "CT" for pier cap, "DZ" for column pier, and "TM" for cap, etc.

[0060] Component serial number dimension: To distinguish components of the same type, function, and location, a unique serial number is assigned to each component. In the coding rules, the component serial number is represented by numbers, such as "001" for the first component, "002" for the second component, and so on.

[0061] For example, a pier cap located in section 1 is coded as “D-JC-1-CT-001” during the design phase; a pier located in section 2 is coded as “C-QD-2-DZ-001” during the construction phase; and a cap located in area A is coded as “O-QT-A-TM-001” during the operation and maintenance phase.

[0062] S103: Bind the private attributes of each engineering stage to the component code of that engineering stage and store them in the extended attributes of the component. At the same time, associate the public attributes of the component to finally generate a BIM master model containing multi-stage attribute information.

[0063] Each component includes public attributes and stage-private attributes.

[0064] Common attributes: Basic attributes common to all stages, including component spatial location coordinates, geometric dimension information (length / width / height), building outline parameters, etc.

[0065] Stage-specific attributes: Define stage-specific attributes for each stage based on its specific requirements. The required attribute information for components differs depending on the engineering stage. For example, the construction stage requires information on construction procedures, quantities, and costs, while the operation and maintenance stage requires information related to maintenance.

[0066] In practical implementation, the custom parameter function of the BIM model is used to write the generated code as a key extended attribute into the attribute library of the corresponding component. Based on the actual project stage and requirements, private attribute information for different stages is specifically bound to the corresponding component code to ensure a one-to-one correspondence between "code" and "attribute". The bound attribute information is then uniformly written into the component's extended attributes, ultimately generating a BIM master model containing attribute information from multiple stages.

[0067] S2, based on the rule engine, sets BIM model splitting rules. The filtering conditions in the splitting rules must include at least one or more of the following dimensions: project stage, functional classification, spatial location, component type and component number.

[0068] The rules engine allows users to define splitting rules based on project requirements. Through the settings interface, users can select conditions such as the engineering stage, functional category, spatial location, and component type of the component, and combine these conditions logically to form sub-model splitting rules.

[0069] In practical applications, rule engines allow users to define rules through methods such as "condition combinations" and "dimension selection." For example:

[0070] The splitting rules can be combined with multiple dimensions such as stages, functions, and spaces to meet the needs of complex scenarios;

[0071] Supports AND / OR logic combinations, such as "belongs to both the construction phase and the pier structure";

[0072] Supports fuzzy matching, such as "components whose codes contain the keyword 'expansion joint'";

[0073] Example of rule engine settings: To filter the pier models in area A of the construction phase, the corresponding rule is set with the code prefix "C-" (construction phase), the second level "QD" (pier), and the third level "A" (area A).

[0074] S3 parses the code of each component in the BIM model, compares the code with the filtering conditions in the splitting rules according to the level, packages the component data corresponding to the successfully matched code, and saves it as a sub-model.

[0075] Specifically, after a user configures rules in the rules engine, the system will perform the splitting process as follows:

[0076] The code of each component in the BIM model is parsed, and the code is compared with the filtering conditions in the splitting rules according to the hierarchy. All successfully matched component codes are marked, and the private attributes of the corresponding stage (such as installation data in the construction stage) are automatically retrieved. The basic public attributes of the component (such as spatial location, geometric dimension information, etc.) are associated to form complete component data. Finally, the filtered component data is packaged to generate independent sub-model files.

[0077] For example, by breaking down the components according to their functions at each design stage (coded with the prefix "D-") (coded at the second level "JC / QT / QD, etc."), the resulting sub-models would be:

[0078] Basic sub-model (coded to match “D-JC-XXX-XXX-XXX”): Contains all basic functional components in the design phase;

[0079] Bridge abutment sub-model (coded to match “D-QT-XXX-XXX-XXX”): contains all bridge abutment functional components in the design phase;

[0080] Pier sub-model (coded to match “D-QD-XXX-XXX-XXX”): Contains all functional components of the piers during the design phase.

[0081] This embodiment constructs a full lifecycle coding system, binding unique codes to different engineering stages of components. By recognizing the codes, sub-models can be automatically split according to dimensions such as stage, function, or space, greatly simplifying the query, update, and scenario-based application process of BIM models in cross-stage collaboration.

[0082] S4 establishes the association mapping between the main model and sub-models, and between sub-models, through the combination of "metadata-driven + graph database".

[0083] In one alternative implementation, step S4 includes:

[0084] S401 defines the association mapping between the main model and the sub-model, and between the sub-models through metadata, including the association relationship between the main model and the sub-model, the data mapping relationship, and the update rules.

[0085] Each model contains basic attributes (model ID, type) and associated metadata. The metadata defines the association mapping between this main model / sub-model and other main models / sub-models, including the association relationship with other models, data mapping relationship and update rules.

[0086] Specifically, after splitting the sub-models from the main model, the association between the main model and each sub-model is established through full lifecycle coding, thereby ensuring data consistency across sub-model components (including all geometric data, attribute data, etc. of the components).

[0087] The relationship between the main model and the sub-model is hierarchical. The main model ID and the sub-model ID form a tree structure. The relationship between the main model and the sub-model is established through full lifecycle coding.

[0088] At the same time, when splitting sub-models, the relationships between sub-models are established according to the stage dimension, functional dimension, and spatial dimension. For example, when splitting according to the functional dimension, the structural sub-model and the electromechanical model have a one-way dependency relationship, while the design stage sub-model and the construction stage sub-model have a two-way non-hierarchical relationship.

[0089] The relationships between sub-models include unidirectional dependencies and bidirectional non-hierarchical relationships.

[0090] If the electromechanical model depends on the location information of the structural sub-model, the electromechanical model should be updated when the structural sub-model is updated, but the update of the electromechanical model does not affect the update of the structural sub-model. The dependency ID and the ID of the dependent are recorded and the dependency type is attached.

[0091] Two-way non-hierarchical relationships (such as the installation association of pipelines and equipment, and the sub-models in the design and construction phases, where updating any one sub-model will update the other).

[0092] Data mapping relationships are used to define the association and transformation rules of specific attributes between different models. The transformation rules include unit conversion, format conversion, logical calculation, etc.

[0093] Update rules refer to the behavioral logic that drives the synchronization engine. Based on the relationships between models, they define the conditions for triggering synchronization and the strategies for executing update actions. For example, there are bidirectional synchronization update rules between the main model and sub-models, and update rules under unidirectional dependency relationships. When the structural sub-model is updated, the electromechanical model must be updated accordingly, but the update of the electromechanical model does not affect the update of the structural sub-model.

[0094] S402 is a graph database built based on metadata, which stores the relationships between sub-models and the main model, as well as between sub-models.

[0095] In a graph database, the main model is a single node, the child models are independent nodes, and the relationships (such as parent-child relationships, unidirectional dependencies, and bidirectional non-hierarchical relationships) are edges, and the relationship structure is stored.

[0096] Compared to traditional relational databases, graph databases offer higher query efficiency and flexibility when handling highly interconnected data. By storing data in a graph database, the system can quickly query and update the relationships between sub-models and the main model, as well as between sub-models themselves, supporting complex network analysis and data tracing.

[0097] In this step, data associations between sub-models and the main model, as well as between sub-models themselves, are established through a combination of "metadata-driven + graph database". Through metadata-driven operation, the system automatically identifies and processes the data associations between sub-models and the main model, thereby achieving data consistency and traceability.

[0098] S5: When the source model is modified, a synchronization operation command is automatically triggered and transmitted to the synchronization engine. The synchronization engine performs the synchronization update of the target model according to the association mapping between the source model and its associated target model.

[0099] The source model is either the main model or a sub-model, and the target model is either the main model or a sub-model.

[0100] In one optional implementation, step S5 includes:

[0101] S501: When the source model is modified, the system automatically triggers a synchronization operation command and transmits it to the synchronization engine.

[0102] S502, the synchronization engine queries the graph database to obtain all target models associated with the source model; for each target model, the synchronization engine further queries the metadata of that target model;

[0103] S503, the synchronization engine, performs synchronous updates to the target model based on the data mapping relationships and update rules defined in the metadata.

[0104] In this embodiment, when a sub-model is modified, it does not need to be relayed through the main model. Instead, the sub-models can directly interact and synchronize to achieve synchronous updates between each other (for example, bidirectional data synchronization can be achieved between the design sub-model and the construction sub-model). This effectively reduces the data synchronization delay between models, thereby ensuring that data synchronization can be carried out efficiently and stably in large-scale component scenarios.

[0105] In one alternative implementation, the system maintains a global version record table to record the current valid version number of the main model and each sub-model, performs conflict detection through an optimistic locking mechanism, and combines a conflict handling process to ensure eventual data consistency.

[0106] During synchronization updates, once the source model (such as a sub-model in the design phase) has completed its own data update and incremented its version number, it sends a command to the synchronization engine. The command must explicitly include the base version number on which the modification is based (i.e., the version number before the modification). The synchronization engine queries the global version record table to obtain the current valid version number of the source model and compares it with the base version number submitted in the synchronization update command.

[0107] If the version numbers are the same, it means there is no conflict. The target model will perform an update, then increment its own version number and update the version record to finally achieve data consistency.

[0108] If there is a discrepancy, a conflict is identified, and the process is transferred to the conflict resolution procedure (such as automatic arbitration or notifying the user to resolve manually).

[0109] like Figure 3 As shown, the second embodiment of this disclosure provides a BIM model full lifecycle decomposition and cross-model synchronization system for executing the BIM model full lifecycle decomposition and cross-model synchronization method. The system includes:

[0110] The main model construction module 101 is used to encode BIM model components based on the full life cycle coding rules, bind the private attributes of each engineering stage with the component code of that engineering stage, store them in the component extended attributes, and generate a BIM main model containing multi-stage attribute information.

[0111] The coding structure consists of engineering stage, functional classification, spatial dimension, component type, and component number;

[0112] The splitting rule setting module 102 is used to set BIM model splitting rules based on the rule engine. The filtering conditions in the splitting rules shall include at least one or more of the following dimensions: project stage, functional classification, spatial location, component type and component number.

[0113] The sub-model splitting module 103 is used to parse the code of each component in the BIM model, compare the code with the filtering conditions in the splitting rules according to the level, and package the component data corresponding to the successfully matched code into a sub-model.

[0114] The model association establishment module 104 is used to establish association mappings between sub-models and the main model, and between sub-models, through the combination of "metadata-driven + graph database".

[0115] The synchronization update module 105 is used to automatically trigger a synchronization operation command and transmit it to the synchronization engine when the source model is modified. The synchronization engine performs the synchronization update of the target model according to the association mapping between the source model and its associated target model.

[0116] The source model is either the main model or a sub-model, and the target model is either the main model or a sub-model.

[0117] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0118] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0119] It should be understood that the above embodiments are only used to illustrate the technical solutions of this disclosure, and not to limit them; although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this disclosure.

Claims

1. A method for the full lifecycle decomposition and cross-model synchronization of a BIM model, characterized in that, Includes the following steps: S1: Encode BIM model components based on the full lifecycle coding rules, bind the private attributes of each engineering stage with the component code of that engineering stage, store them in the component extended attributes, and generate a BIM master model containing multi-stage attribute information; The coding structure consists of engineering stage, functional classification, spatial dimension, component type, and component number; S2: Set BIM model splitting rules based on the rule engine. The filtering conditions in the splitting rules should include at least one or more of the following dimensions: project stage, functional classification, spatial location, component type and component number. S3: Parse the code of each component in the BIM model, compare the code with the filtering conditions in the splitting rules according to the level, package the component data corresponding to the successfully matched code, and save it as a sub-model; S4: By combining "metadata-driven + graph database", establish the association mapping between sub-models and the main model, and between sub-models; S5: When the source model is modified, a synchronization operation command is automatically triggered and transmitted to the synchronization engine. The synchronization engine performs the synchronization update of the target model according to the association mapping between the source model and its associated target model. The source model is either the main model or a sub-model, and the target model is either the main model or a sub-model. When a sub-model is modified, it does not need to be transferred through the main model. Instead, the sub-models can be directly interacted and synchronized to achieve synchronous updates between them. Step S1 includes the following steps: S101: Read BIM model data, including component tree hierarchy, component function, component type, spatial location and other attachment attributes; S102: Based on the full life cycle coding rules and BIM model data, automatically generate component codes. The coding structure consists of engineering stage, functional classification, spatial location, component type and component serial number. S103: Bind the private attributes of each engineering stage to the component code of that engineering stage, store them in the extended attributes of the component, and associate them with the public attributes of the component to finally generate a BIM master model containing multi-stage attribute information. Step S3 specifically includes: The code of each component in the BIM model is parsed, and the code is compared with the filtering conditions in the splitting rules according to the level. All successfully matched component codes are marked, the private attributes of the corresponding stage are automatically retrieved, and the basic public attributes of the component are associated to form complete component data. Finally, the filtered component data is packaged to generate independent sub-models. In step S4, the relationship between the main model and the sub-model is hierarchical, and the relationship between the sub-models includes unidirectional dependency and bidirectional non-hierarchical relationship.

2. The method for full lifecycle decomposition and cross-model synchronization of BIM models according to claim 1, characterized in that, Step S4 specifically includes the following steps: S401 defines the association mapping between the main model and the sub-model, and between the sub-models through metadata, including the association relationship between the main model and the sub-model, the data mapping relationship, and the update rules. S402 is a graph database built based on metadata, which stores the relationships between sub-models and the main model, as well as between sub-models.

3. The method for full lifecycle decomposition and cross-model synchronization of BIM models according to claim 1, characterized in that, Step S5 includes the following steps: S501: When the source model is modified, the system automatically triggers a synchronization operation command and transmits it to the synchronization engine. S502, the synchronization engine queries the graph database to obtain all target models associated with the source model; for each target model, the synchronization engine further queries the metadata of that target model; S503, the synchronization engine, performs synchronous updates to the target model based on the data mapping relationships and update rules defined in the metadata.

4. The method for full lifecycle decomposition and cross-model synchronization of BIM models according to claim 1, characterized in that, In step S5, the system maintains a global version record table to record the current valid version number of the main model and each sub-model. Conflict detection is performed through an optimistic locking mechanism, and data consistency is ensured by combining it with a conflict handling process.

5. A BIM model lifecycle decomposition and cross-model synchronization system, used to execute the BIM model lifecycle decomposition and cross-model synchronization method as described in any one of claims 1-4, characterized in that, The system includes: The main model construction module is used to encode BIM model components based on the full life cycle coding rules, bind the private attributes of each engineering stage with the component code of that engineering stage, store them in the component extended attributes, and generate a BIM main model containing multi-stage attribute information. The coding structure consists of engineering stage, functional classification, spatial dimension, component type, and component number; The splitting rule setting module is used to set BIM model splitting rules based on the rule engine. The filtering conditions in the splitting rules must include at least one or more of the following dimensions: project stage, functional classification, spatial location, component type and component number. The sub-model splitting module is used to parse the code of each component in the BIM model, compare the code with the filtering conditions in the splitting rules according to the level, and package the component data corresponding to the successfully matched code into a sub-model. The model association establishment module is used to establish association mappings between sub-models and the main model, and between sub-models themselves, through a combination of "metadata-driven + graph database". The synchronization update module is used to automatically trigger a synchronization operation command and send it to the synchronization engine when the source model is modified. The synchronization engine then performs a synchronization update of the target model based on the association mapping between the source model and its associated target model. The source model is either the main model or a sub-model, and the target model is either the main model or a sub-model.

Images