BIM (Building Information Modeling) data model version management method based on version identifier

Through the version management method of BIM model based on version identifiers, the problem that existing tools cannot identify and manage the version changes of entity objects is solved, and efficient version control and data fallback are achieved to meet the data integration needs of the entire life of the project.

CN119047119APending Publication Date: 2024-11-29CHINA TRANSPORT INFORMATION TECH GRP CO LTD
View PDF 0 Cites 3 Cited by

Patent Information

Application Number
CN202410899773.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-05
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

The existing BIM model version management tools cannot effectively identify and manage the version changes of geometric, attribute and relational data of entity objects in the project, resulting in inefficient version control and cannot meet the data communication needs throughout the entire life of the project.

Method used

Using the version management method of BIM model based on version identifiers, divide the BIM model through ontology theory, create version identifiers to manage the geometric, attributes and relational data of entity objects, realize the continuous iteration of the main version and the differential derivative of the sub-version, and support the version Integration, conflict resolution and fallback evolution.

Benefits of technology

It realizes sub-object-level version management, which can accurately identify and manage version changes of entity objects, improve version control efficiency, reduce version comparison scope, support sub-version management of BIM model in different environments, and restore data through the history library. Meet the version fallback and evolution needs of engineering projects.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119047119A_ABST
    Figure CN119047119A_ABST
Patent Text Reader

Abstract

The invention discloses a BIM model version management method based on a version identifier, which comprises the following steps: creating a BIM model and a BIM model main version, initializing the version identifier of the BMI model main version, the version identifier comprising an entity object version number corresponding to an entity object, a geometric data version number, an attribute data version number and a relational data version number; in response to a model extraction demand, a BIM model sub-version is extracted from a BIM model main version, the BIM model version is used or edited in an application system, a version identifier of the BIM model sub-version is maintained in the application system, the BIM model main version and the BIM model sub-version are operated so as to update the corresponding version identifier, and the BIM model sub-version is used or edited in the application system. The used or edited BIM model sub-version and the BIM model main version are subjected to version integration based on the version identifier so as to update the BIM model main version, the version of the entity object is managed through the version identification method, and therefore the technical problem of BIM model version management in the project full life cycle is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of BIM technology, and in particular to a BIM data model version management method based on version identifier. Background Art

[0002] The problem of BIM model data connectivity throughout the life cycle of a project has always been one of the pain points that plagues the engineering community. This problem is caused by the inherent characteristics of the engineering industry. A project can be divided into stages such as survey, design, construction, operation and maintenance, and each stage has many participants responsible for different construction contents. Due to the lack of top-level planning and a unified collaborative platform, this will inevitably lead to each participant fighting on their own. The participants use different application systems to produce the BIM model data of the construction content they are responsible for. The application systems are naturally separated at the BIM model data format level, which further causes the problem of BIM model data connectivity.

[0003] The original intention of BIM technology is to establish and maintain a BIM model that integrates BIM data throughout the life cycle of the project. Project personnel at each stage of the project can obtain data on demand to achieve the purpose of improving project execution efficiency and saving project costs. The original intention of BIM technology provides a technical idea for solving the problem of data connectivity, that is, to establish and maintain a single data source throughout the life cycle of the project. All participants in the project extract the required BIM model data from this data source and submit the BIM model data required for the subsequent stages of the project. Since the BIM model in this single data source is constantly precipitated and iterated with the advancement of project construction, the version management of the BIM model is a problem that must be solved to realize this technical idea.

[0004] At present, there are relatively mature code version management tools in the field of software engineering, such as git, svn, etc. However, due to the inherent characteristics of the engineering industry, code version management tools cannot be directly used for BIM model version management, which is reflected in the following aspects:

[0005] 1. Different service objects

[0006] Engineering projects are generally carried out in stages, and each stage is implemented by multiple parties. The BIM data generated by each party must be managed in a unified and orderly manner, and the service objects are the survey units, design units, construction units, operation and maintenance units and other participants of the engineering project. Code version management tools are generally suitable for the management of software development project codes and documents, and the service objects are product personnel, R&D personnel, testers, etc.

[0007] 2. Different management requirements

[0008] Due to the business characteristics of engineering projects, BIM model version management only needs to have three major capabilities: version control, version extraction, and version integration to meet the requirements. Considering the actual situation of project users, version management tools are required to be simple, convenient, interface-based, interactively optimized, and easy to use. BIM model version management is generally embedded in other systems as a module and is not used as a separate tool.

[0009] 3. Different management connotations

[0010] The capabilities of BIM model version management and code management tools are different. Take the version extraction of BIM model version management as an example. The version extraction of BIM model version management corresponds to the creation of branches in code management tools. Version extraction is to extract part of the BIM model data in the BIM model and create a branch; while the creation of branches in code management tools is to extract all the data of the main version, or a snapshot of the main version, to create a branch.

[0011] 4. Different management content

[0012] BIM model version management focuses on the geometric data composed of model points, lines, surfaces, and bodies; business data such as design parameters, quantity calculation, pricing, quality, and progress; and the relationship data between business objects; these data are organized according to a certain data structure and saved in files or databases, such as dgn, rvt, and other files. Code management tools focus on text, pictures, and other content. There are obvious differences in the management content of the two.

[0013] In addition, the existing BIM model version management can only manage the model-level version number, without considering the entity object level or sub-object level, and cannot identify and manage the version changes of the geometry, attributes, and relationship data in the entity object. Summary of the invention

[0014] In order to overcome the shortcomings of the above technologies, the present invention provides a BIM model version management method based on version identifier. The BIM model is divided through ontology theory, and version identifiers are proposed to manage it. The version identifiers corresponding to the main model and sub-model are maintained in the version management system and the application system respectively, and are extracted and integrated based on specimen identifiers to solve the technical problem of BIM model version management during the entire life cycle of the project.

[0015] The technical solution adopted by the present invention to overcome its technical problems is: a BIM model version management method based on a version identifier proposed by the present invention includes creating a BIM model and creating a BIM model master version in a corresponding version management system, initializing a version identifier corresponding to an entity object in the BMI model master version, and using or operating the BIM model master version in the version management system to update the corresponding version identifier, wherein the entity object includes at least geometric data, attribute data and relationship data, and the version identifier includes at least an entity object version number, a geometric data version number, an attribute data version number and a relationship data version number corresponding to the entity object; in response to a model extraction requirement, extracting a BIM model sub-version from the BIM model master version to an application system, using or operating the BIM model sub-version in the application system, and correspondingly maintaining and updating the version identifier of the BIM model sub-version; integrating the used or edited BIM model sub-version with the current BIM model master version based on the version identifier to update the BIM model master version, wherein the version integration includes version comparison, conflict resolution and version merging.

[0016] Through the cooperation of the version management system and the application system, the version management concept of "continuous iteration of the main version and differential derivation of sub-versions" is realized.

[0017] Furthermore, the version management system and the application system also maintain the updated version identifier and the corresponding life cycle in the version control table respectively, and locate the BIM model main version to the BIM model version number based on at least the version identifier and life cycle in the version control table, thereby restoring the BIM model data based on the BIM model version number.

[0018] Furthermore, when an entity object from the main version of the BIM model or the sub-version of the BIM model changes, a version identifier record corresponding to the entity object is added to the version control table, and the life cycle of the previous version identifier record corresponding to the entity object is updated, wherein the life cycle includes a first cycle value and a second cycle value, wherein the first cycle value of the previous version identifier record is unchanged, and the second cycle value is the current BIM model version number, wherein the BIM model version number corresponds to the largest entity object number in the current BIM model, and the first cycle value of the newly added version identifier record is the current BIM model version number, and the second cycle value identifies the existence status of the current BIM model.

[0019] By identifying the scope of application of the entity object in the BIM model version iteration process through the life cycle, the version control process is optimized and the version control efficiency is improved.

[0020] Furthermore, the version management system and application system are also used for version rollback and version evolution based on maintaining a history library, and the history library is used to store entity object data of deleted entity objects, at least saving the unique identifier and version identifier of the corresponding entity object, as well as the entity object's own data and entity object component data.

[0021] By maintaining the history library, the entity object data of the corresponding version number can be restored during version control (version rollback or version evolution). A record is uniquely identified by the entity object's global unique identifier and version identifier, and the entity object meta information is returned through the metadata library to restore the reconstruction and attachment of the entity object node in the instance library.

[0022] Furthermore, the operations of the BIM model main version and the BIM model sub-version specifically include: adding a new entity object or adding geometric data, attribute data, and relationship data in the entity object; deleting an entity object or deleting the geometric data, attribute data, and relationship data of the entity object; editing the geometric data, attribute data, and relationship data of the entity object.

[0023] Furthermore, if a new entity object is added, the entity object version number of the new entity object is incremented based on the maximum value of all entity object version numbers in the BIM model, or if one or more of the geometric data, attribute data, and relationship data of the new entity object is added, then it is incremented based on one or more of the maximum geometric data version number, the maximum attribute data version number, and the maximum relationship data version number among all version identifiers in the BIM model, and the entity object version number is incremented based on the maximum value of all entity object version numbers in the BIM model.

[0024] Furthermore, if an entity object in the BIM model is deleted, the corresponding entity object version number is deleted and marked, or if one or more of the geometric data, attribute data, and relationship data of the entity object is deleted, then one or more of the maximum geometric data version number, the maximum attribute data version number, and the maximum relationship data version number in all version identifiers in the BIM model are incremented and marked, and the entity object version number is incremented based on the maximum value of all entity object version numbers in the BIM model.

[0025] Furthermore, when editing one or more of the geometric data, attribute data, and relationship data of an entity object in the BIM model, the version numbers are incremented based on one or more of the maximum geometric data version number, the maximum attribute data version number, and the maximum relationship data version number among all version identifiers in the BIM model, and the entity object version number is incremented based on the maximum value of all entity object version numbers in the BIM model.

[0026] Furthermore, the method of integrating the used or edited BIM model sub-version with the BIM model main version based on the version identifier to update the BIM model main version at least includes: obtaining the BIM model sub-version processed by the application system, comparing the BIM model sub-version and the current BIM model main version in units of entity objects, including at least geometric data, attribute data, and relationship data, so as to identify a set of entity objects with state changes; resolving conflicts one by one for the set of entity objects with state changes; merging the entity objects after conflict resolution into the BIM model main version, and updating the version identifiers of the corresponding entity objects in the BIM model main version.

[0027] Furthermore, the method of obtaining a BIM model sub-version processed by the application system, and comparing the BIM model sub-version and the current BIM model main version in units of entity objects, including at least geometric data, attribute data, and relationship data, thereby identifying a set of entity objects with state changes, specifically includes: comparing the version identifier of the updated BIM model sub-version with the version identifier of the initially extracted BIM model sub-version, and marking the state of the entity objects in the updated BIM model sub-version as one or more of unchanged, updated, added, and deleted, thereby obtaining a set of entity objects with state changes in the sub-model; comparing the version identifier of the current BIM model main version with the version identifier of the initially extracted BIM model sub-version, marking the state of the entity objects of the current BIM model main version as one or more of unchanged, updated, deleted, and added, thereby obtaining a set of entity objects with state changes in the main model.

[0028] The BIM model version management granularity is at the sub-object level, which can identify and manage version changes in geometry, attributes, and relationship data in entity objects, reduce the scope of version comparison, reduce the scope of master-sub version comparison during version integration, improve performance, and accurately and quickly determine the entity object set for rollback version during version control.

[0029] The beneficial effects of the present invention are:

[0030] 1. Use ontology theory to guide BIM model creation. Engineering entity objects should consist of three parts: geometry, attributes, and relationships. The concept and inherent attributes of the entity object itself are the content of the ontology level. The geometry, attributes, and relationships of the components of the entity object have optional characteristics and belong to the content of the expression level.

[0031] 2. A version identifier method is proposed to manage the version of entity objects. The version identifier of an entity object consists of the entity object O_rid, geometric data G_rid, attribute data A_rid, and relationship data R_rid, and is expressed in the form of O_rid-G_rid-A_rid-R_rid;

[0032] 3. The BIM model version management granularity is at the sub-object level, which can identify and manage the version changes of geometry, attributes, and relationship data in entity objects, reduce the scope of version comparison, reduce the scope of master-sub version comparison during version integration, improve performance, and accurately and quickly determine the entity object set of the rollback version during version control;

[0033] 4. The management of BIM model sub-versions is carried out in different software and hardware environments. The life cycle of BIM model sub-versions goes through three processes: extraction, update, and integration. The extraction and integration processes are managed in the version management system, while the update process is managed in the application system.

[0034] 5. Maintain the history library to restore the entity object data of the corresponding version number during version control (version rollback or version evolution). Uniquely identify a record through the global unique identifier and version identifier of the entity object, and then return the entity object meta information through the metadata library to restore the reconstruction and attachment of the entity object node in the instance library;

[0035] 6. The entity object life cycle identifies the applicable scope of the entity object in the BIM model version iteration process, optimizes the version control process, and improves version control efficiency;

[0036] 7. Through the cooperation of the version management system and the application system, the data of the main model can be continuously accumulated and iterated as the project progresses, and the sub-model can be adapted to different application scenarios, thus realizing the version management concept of "continuous iteration of the main version and differential derivation of sub-versions". BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A schematic diagram of a flow chart of a BIM data model version management method based on a version identifier according to an embodiment of the present invention;

[0038] Figure 2 A schematic diagram of a system used in a BIM data model version management method based on a version identifier according to an embodiment of the present invention;

[0039] Figure 3 A schematic diagram of an entity object in an embodiment of the present invention;

[0040] Figure 4 A schematic diagram of a version identifier change for operating a BIM data model according to an embodiment of the present invention;

[0041] Figure 5 A schematic diagram of lifecycle maintenance of an entity object according to an embodiment of the present invention;

[0042] Figure 6The figure is a schematic diagram of a version merging process including a history library according to an embodiment of the present invention. DETAILED DESCRIPTION

[0043] BIM: Building Information Modeling is a technology that realizes information management of the entire life cycle of a building by digitizing building information.

[0044] BIM model master version: This is the version that should be created at the beginning of the project, and the iteration process runs through the entire life cycle of the project. As the project progresses, the BIM model data will continue to be improved and serve as a single data source for application scenarios at all stages of the project.

[0045] BIM model sub-version: It is a subset of the BIM model main version. Extract the required data according to the application scenario data requirements at each stage of the project. Decide whether the BIM model sub-version should be merged back to the BIM model main version according to the project business needs.

[0046] Version management system: The main operating environment for BIM model version management, responsible for saving the main version of the BIM model, extracting BIM model sub-versions, integrating BIM model sub-versions, etc.

[0047] Application system: BIM model sub-version application operating environment, which edits and operates BIM model sub-version and updates BIM model sub-version data during the application process.

[0048] Version Control

[0049] Version control is the operation of BIM models on the main version, allowing users to locate BIM models to the specified model version number. Version control includes two capabilities: version rollback and version evolution.

[0050] Version rollback

[0051] Version rollback is to roll back the BIM model to the specified version number along the timeline. The main function of version rollback is to quickly restore BIM data and avoid unnecessary losses.

[0052] Version evolution

[0053] Version evolution is the opposite of version rollback, which is to evolve the BIM model along the timeline to a specified version number. Version evolution and version rollback are related in order to quickly find and restore BIM data with a specified version number.

[0054] Version Extraction

[0055] The BIM model on the main version is a full set of data, and the data required for specific business scenarios is a subset of the BIM model. Version extraction is to extract a subset from the BIM model data on the main version as a sub-version. The BIM model data on the sub-version can be provided to the application system for use.

[0056] Version Integration

[0057] Version integration is the capability corresponding to version extraction. Version integration is to merge the BIM model data on the sub-version into the main version. To further decompose the version integration capability, three issues should be solved: version comparison, conflict resolution, and version merging.

[0058] Version comparison

[0059] The prerequisite for version integration is to identify the amount of changes in the version content, that is, to identify the amount of additions, deletions, and edits between different versions. Version comparison requires the ability to identify the amount of changes in the version.

[0060] Conflict Resolution

[0061] Conflict resolution is to formulate a series of rules for handling changes during the version merging process, and provide an interactive processing method when the processing rules cannot handle it.

[0062] Version Merge

[0063] Version merging is the process of merging the contents of two versions into one version after version comparison and conflict resolution.

[0064] Ontology

[0065] It is a proposition in the category of philosophical metaphysics, used to explore the origin and existence of the world. In the computer field, ontology can be used to define a set of concepts in a specific field and the relationship between concepts, so as to express the true connotation of concepts clearly and unambiguously and achieve a common understanding of domain concepts.

[0066] According to the guidance of ontological thought, engineering entity objects should consist of three parts: geometry, attributes, and relationships. The concept of entity objects and their inherent characteristics are the content of the entity object ontology, which will not change or disappear with objective conditions. The components of entity objects, such as geometry, attributes, and relationships, express the concept of entity objects from a certain perspective, and generally change with changes in objective conditions. From this perspective, the existence of the geometry, attributes, and relationships of entity objects does not affect the existence of the entity objects themselves, so the components of entity objects (geometry, attributes, and relationships) are optional.

[0067] According to the business characteristics of data integration throughout the entire life cycle of the project, BIM model version management should be managed based on the sub-entity objects in the BIM model as the basic unit, that is, it should be able to identify and manage changes in geometric data, attribute data, and relationship data in entity objects.

[0068] In order to facilitate those skilled in the art to better understand the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments. The following is only exemplary and does not limit the protection scope of the present invention.

[0069] like Figure 1 As shown, the BIM model version management method based on version identifier described in this embodiment is applied in Figure 2 The system shown includes the following steps.

[0070] S1, create a BIM model and create a BIM model master version in the corresponding version management system, initialize the version identifier corresponding to the entity object in the BMI model master version, and use or operate the BIM model master version in the version management system to update the corresponding version identifier, wherein the entity object includes at least geometric data, attribute data and relationship data, and the version identifier includes at least the entity object version number, geometric data version number, attribute data version number and relationship data version number corresponding to the entity object.

[0071] According to the business characteristics of data penetration throughout the project life cycle, such as Figure 3 As shown in the figure, BIM model version management should be managed based on the sub-entity objects in the BIM model as the basic unit, that is, it should be able to identify and manage changes in geometric data, attribute data, and relationship data in entity objects.

[0072] In one embodiment of the present invention, the BIM master model is constructed using a neo-4j graph database. The geometric data and attribute data of the entity objects, as well as the relationship data between the entity objects, are obtained through the graph database, and the version identifier corresponding to the main version of the BIM model is obtained using this information.

[0073] The version identifier acts on the entity object and is the only identifier that expresses the entity object version information. The version identifier of an entity object consists of the entity object O_rid, geometry data G_rid, attribute data A_rid, and relationship data R_rid, and is expressed in the form of O_rid-G_rid-A_rid-R_rid. Among them, O_rid is the entity object version number, G_rid is the geometry data version number, A_rid is the attribute data version number, and R_rid is the relationship data version number.

[0074] In one embodiment of the present invention, the entity object version number O_rid, G_rid is the geometry data version number, A_rid is the attribute data version number, and R_rid is the relationship data version number, all of which are positive integers with a value range of [0, +∞].

[0075] The BIM model version number is denoted as M_rid, and its value range is [1, max(O_rid)]. max(O_rid) is the maximum value of O_rid of all entity objects in the BIM model.

[0076] S2, in response to the model extraction requirement, extract the BIM model sub-version from the BIM model main version to the application system, use or operate the BIM model sub-version in the application system, and correspondingly maintain and update the version identifier of the BIM model sub-version.

[0077] Operate the BIM model master version and BIM model sub version to update the corresponding version identifier. The BIM model operations include adding, deleting and editing. The objects of operation are entity objects and their geometric data, attribute data and relationship data. Each operation is described as follows.

[0078] S21, adding a new entity object or geometric data, attribute data, and relationship data in the new entity object.

[0079] Taking the example of adding a new entity object to the main version of the BIM model, the entity object version number of the new entity object is incremented based on the maximum value of all entity object version numbers in the BIM model. Or if one or more of the geometric data, attribute data, and relationship data of the new entity object is incremented based on the maximum geometric data version number, attribute data version number, and relationship data version number of all version identifiers in the BIM model, respectively, the entity object version number is incremented based on the maximum value of all entity object version numbers in the BIM model.

[0080] like Figure 4 As shown in T1, entity objects A and B are added, where entity object A includes geometric data, attribute data, and relationship data. Because it belongs to the initial stage, the version identifier of entity object A is 1-1-1-1;

[0081] Entity object B contains only geometry and attribute data, so the version identifier of entity object B is 1-1-1-0.

[0082] like Figure 4 As shown in T3, based on what is shown in T2, the relationship data of entity object B and the new entity object C are added at the same time.

[0083] Entity object C only includes geometry data and attribute data, so the version identifier of entity object C is 3-3-2-0, where the entity object version number is calculated and incremented based on the largest entity object version number 2 after the last change. The geometry data version number is incremented based on the largest entity object version number 2 after the last change, and the attribute data version number is incremented based on the largest attribute data version 2 after the last change. Since entity object C does not have a relationship version number, it is 0, so the version identifier of the newly added entity object C is 3-3-2-0.

[0084] The entity object version number of entity object B is calculated and incremented based on the last largest entity object version number 2. The relationship data version number is calculated and incremented based on the last largest relationship data version number 1 in the version identifier, so the version identifier of entity object B is 3-2-1-2.

[0085] It should be noted that for changes in the version identification number of a BIM model that performs multiple operations simultaneously, the changes are incremented based on the previous corresponding version number.

[0086] S22, editing the geometric data, attribute data, and relationship data of the entity object.

[0087] If one or more of the geometry data, attribute data, and relationship data of an entity object is edited, the version number of the entity object is incremented based on the maximum geometry data version number, the maximum attribute data version number, and the maximum relationship data version number among all version identifiers in the BIM model, and the entity object version number is incremented based on the maximum value of all entity object version numbers in the BIM model. The version identifier of the entity object that is not updated remains unchanged.

[0088] like Figure 4 As shown in T2, entity object A remains unchanged, and the version identifier of entity object A is 1-1-1-1. The geometric data of entity object B is edited, and after the editing is completed, the entity object version number and the geometric data version number in the version identifier of entity object B are incremented, and its version identifier is modified to 2-2-1-0.

[0089] S23, deleting the entity object or deleting the geometric data, attribute data, and relationship data in the entity object.

[0090] If you delete an entity object in the BIM model, the corresponding entity object version number will be deleted and marked.

[0091] Or if one or more of the geometric data, attribute data, and relationship data of the entity object is deleted, the version numbers are incremented and marked based on the maximum geometric data version number, attribute data version number, and relationship data version number of all version identifiers in the BIM model, and the entity object version number is incremented based on the maximum value of all entity object version numbers in the BIM model.

[0092] like Figure 4 As shown in T4, there is no operation on entity object A and entity object C, so their version identifiers remain unchanged. The geometry data of entity object B is deleted, and the entity object version number in the version identifier is incremented to 4 based on the previous maximum entity object version number 3, while the geometry data version number is changed to 4 based on the previous maximum geometry data version number 3, and the deletion mark D is marked.

[0093] Since each edit of an entity object triggers an update of the version identifier, the version identifier of each update needs to be saved for version control.

[0094] S3, integrating the used or edited BIM model sub-version with the current BIM model main version based on the version identifier to update the BIM model main version, wherein the version integration includes version comparison, conflict resolution and version merging.

[0095] According to the actual needs of the project, the user extracts some required BIM model sub-versions from the BIM model master version, and saves the version identifier of the extracted entity object in the BIM model sub-version, which is used to determine the status of the entity object in the BIM master version in the subsequent version integration work. The extracted BIM model sub-version is transferred to the application system, and the application system operates the data in the BIM model sub-version according to business needs. The operation also has four states: unchanged, updated, added and deleted. The application system is responsible for maintaining the update of the BIM model sub-version version identifier.

[0096] Taking the BIM model sub-version extracted from the BIM model main version according to actual needs, including entity object A and entity object C as an example, the version identifier of entity object A is 1-1-1-1, and the version identifier of entity object C is 3-3-3-0. The corresponding sub-version control table is shown in Table 1.

[0097] Table 1

[0098] Entity Object O_rid G_rid A_rid R_rid Life_Range A 1 1 1 1 [1,4] C 3 3 2 0 [3,4]

[0099] Taking the newly added entity object D in the BIM model sub-version as an example, the entity object D includes geometric data, attribute data and relationship data, so the version identifier of the entity object D is 4-4-3-2. The sub-version control table maintained by the application system is shown in Table 2.

[0100] Table 2

[0101] Entity Object O_rid G_rid A_rid R_rid Life_Range A 1 1 1 1 [1,5] C 3 3 2 0 [3,5] D 4 4 3 2 [5,5]

[0102] S31, integrating the updated BIM model sub-version into the BIM model main version, and then performing a full comparison between the BIM model sub-version and the current BIM model main version in units of entity objects, the comparison content includes geometric data, attribute data, and relationship data, and identifying a set of entity objects with state changes.

[0103] When the BIM model master version and BIM model sub-version are used in parallel, entity objects have four states: added, deleted, unchanged, and updated. The current states of entity objects in the BIM model master version and BIM model sub-version are determined based on the initial version identifier of the BIM model sub-version entity object just extracted.

[0104] In one embodiment of the present invention, version comparison based on entity objects mainly includes the following steps.

[0105] S311, compare the version identifier of the entity object of the updated BIM model sub-version with the initial version identifier corresponding to the entity object of the initially extracted BIM model sub-version, mark the status of the entity object in the updated BIM model sub-version and identify the deleted entity objects, the possible values ​​are: unchanged, updated, added and deleted.

[0106] Taking Table 2 as an example, the status of the marked entity object D is added, and the status of the entity object A and the entity object C are unchanged.

[0107] S312, comparing the version identifier of the current BIM model main version with the initial version identifier corresponding to the entity object of the initially extracted BIM model sub-version, marking the entity object status of the current BIM model main version, with possible values ​​being unchanged, updated, deleted, and added.

[0108] S32, resolving conflicts one by one for the entity object sets whose states have changed.

[0109] The entity object set marked in the BIM model sub-version and the entity object set marked in the BIM model main version are resolved one by one. The conflict resolution methods include automatic conflict resolution using the conflict rule library and manual resolution. The conflict rules are shown in Table 3 as an example.

[0110] Table 3

[0111] Serial number Subversion Status Major version status Processing rules Remark 1 Unchanged Unchanged No treatment 2 Updated Unchanged replace 3 Added / Increase This object state does not exist in the main version 4 delete Unchanged delete 5 Unchanged Updated No treatment 6 Updated Updated Manual Processing 7 Added / Increase This object state does not exist in the main version 8 delete Updated Manual Processing 9 Unchanged Added / This situation does not exist 10 Updated Added / This situation does not exist 11 Added Added / This situation does not exist 12 delete Added / This situation does not exist 13 Unchanged delete Manual Processing 14 Updated delete Manual Processing 15 Added delete / This situation does not exist 16 delete delete No treatment

[0112] S33. Merge the entity objects after conflict resolution into the main version of the BIM model, and update the version identifier of the entity objects corresponding to the main version of the BIM model.

[0113] Taking the updated BIM model sub-version corresponding to the sub-version control table in Table 4 as an example, it is integrated into the BIM model main version. The integrated version is changed based on the version identifier of the current BIM model main version. The entity object D is integrated into the BIM model main version, which is newly added relative to the BIM model main version. Therefore, the version identifier of the entity object D is modified 5-2-2-2 accordingly. The version control table of the updated BIM model main version is shown in Table 5.

[0114] Table 4

[0115] Entity Object O_rid G_rid A_rid R_rid Life_Range A 1 1 1 1 [1,4] D 4 4 3 2 [4,4]

[0116] Table 5

[0117] Entity Object O_rid G_rid A_rid R_rid Life_Range A 1 1 1 1 [1,4] D 5 2 2 2 [5,5]

[0118] S5, the version management system and the application system also maintain the updated version identifier and the corresponding life cycle in the version control table respectively, and obtain a set of entity objects applicable to the BIM model version number from the BIM model master version based on at least the version identifier and life cycle in the version control table, thereby restoring the BIM model data based on the BIM model version number.

[0119] The entity object version identifier stores the corresponding version identifier and life cycle. That is, the storage entity object applies to the BIM model version number range. Each time a sub-version is merged, it will trigger the upgrade of the BIM model version number. The affected entity object will add a new version identifier record in the version library, and the life cycle of a record on the entity object will also be updated. Figure 5 The figure shows an example of the life cycle changes of an entity object after four sub-model mergers.

[0120] In one embodiment of the present invention, the entity object life cycle Life_Range identifies the applicable scope of the entity object during the BIM model version iteration process. When its second cycle value m_rid_r=-1, it indicates that the entity object is applicable to the BIM model version from the first cycle value m_rid_l version to the latest BIM model version.

[0121] When the entity object B changes during the first sub-version merge, the life cycle of the entity object B is also updated accordingly and maintained in the version control table. The life cycle of B previously saved in the version control table is updated from [1,-1] to [1,1], and a new record is added with the life cycle of B corresponding to [2,-1]. The version identifier records after four sub-model merges are shown in Table 6.

[0122] Table 6

[0123] Entity Object O_rid G_rid A_rid R_rid Life_Range A 1 1 1 1 [1,3] B 1 1 1 0 [1,1] B 2 2 1 0 [2,2] B 3 2 1 1 [3,3] A 4 1 2 1 [4,-1] B 4 2 2 1 [4,-1]

[0124] When the main version of the BIM model is misoperated or data is lost, the main version of the BIM model is located to the specified model version number through version control to restore the BIM model data. When rolling back the version, the BIM model rollback version number mrid is given, and the conditions that the entity object identifier to be extracted should meet are as follows:

[0125] mrid>=m_rid_l&&(mrid<=m_rid_r||m_rid_r===-1)

[0126] For example, the BIM model version number 4 is rolled back to the BIM model main version number 1. For example, if the rollback version number mrid is 1, the entity objects that meet the conditions are shown in Table 7.

[0127] Table 7

[0128]

[0129] In some embodiments, the version management system and the application system are also used for version rollback and version evolution based on maintaining a history library, wherein the history library is used to store entity object data of deleted entity objects, and at least saves the unique identifier and version identifier of the corresponding entity object, as well as the entity object's own data and entity object component data.

[0130] like Figure 6 The figure shows a flow chart of the version merge including the maintenance of the history library. The history library mainly stores the entity object unique identifier global_id, entity object version identifiers o_rid, g_rid, p_rid, r_rid, entity object data entity_node, entity object component (geometry, attribute, relationship) data cascading_nodes, etc. During version control (version rollback or version evolution), a record is uniquely identified by the entity object's global_id and identifier orid-grid-prid-rrid, and then the entity object meta information is returned through the metadata library to restore the reconstruction and attachment of the entity object node in the instance library.

[0131] When merging versions, when the entity object is updated, that is, Figure 6 The REPLACE_STATUS process shown in the figure requires deleting the entity object first, storing the deleted entity object in the history library, updating the version library, and then cascading the new object from the instance library and updating the version library.

[0132] It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.

Claims

1. A BIM model version management method based on version identifier, characterized in that: include: Create a BIM model and create a BIM model master version in the corresponding version management system, initialize a version identifier corresponding to an entity object in the BIM model master version, and use or operate the BIM model master version in the version management system to update the corresponding version identifier, wherein the entity object includes at least geometric data, attribute data and relationship data, and the version identifier includes at least an entity object version number, a geometric data version number, an attribute data version number and a relationship data version number corresponding to the entity object; In response to model extraction requirements, extract the BIM model sub-version from the BIM model master version to the application system, use or operate the BIM model sub-version in the application system, and maintain and update the version identifier of the BIM model sub-version accordingly; The used or edited BIM model sub-version is integrated with the current BIM model main version based on the version identifier to update the BIM model main version, wherein the version integration includes version comparison, conflict resolution and version merging.

2. A BIM model version management method based on version identifier according to claim 1, characterized in that: The version management system and the application system also maintain the updated version identifier and the corresponding life cycle in the version control table respectively, and locate the BIM model main version to the BIM model version number based on at least the version identifier and life cycle in the version control table, thereby restoring the BIM model data based on the BIM model version number.

3. A BIM model version management method based on version identifier according to claim 2, characterized in that: When the entity object of the main version of the BIM model or the sub-version of the BIM model changes, a new version identifier record of the corresponding entity object is added to the corresponding version control table, and the life cycle of the previous version identifier record corresponding to the entity object is updated. The life cycle includes a first cycle value and a second cycle value, wherein the first cycle value of the previous version identifier record is unchanged, and the second cycle value is the current BIM model version number, wherein the BIM model version number corresponds to the largest entity object number in the current BIM model. The first cycle value of the newly added version identifier record is the current BIM model version number, and the second cycle value identifies the status of the current BIM model.

4. A BIM model version management method based on version identifier according to claim 2, characterized in that: The version management system and application system are also used for version rollback and version evolution based on maintaining a history library, and the history library is used to store entity object data of deleted entity objects, at least saving the unique identifier and version identifier of the corresponding entity object, as well as the entity object's own data and entity object component data.

5. A BIM model version management method based on version identifier according to claim 1, characterized in that: The operation of the BIM model main version and the BIM model sub-version specifically includes: Add new entity objects or geometric data, attribute data, and relationship data in new entity objects; Delete entity objects or delete geometric data, attribute data, and relationship data of entity objects; Edit the geometric data, attribute data, and relationship data of entity objects.

6. A BIM model version management method based on version identifier according to claim 5, characterized in that: When a new entity object is added, the entity object version number of the new entity object is incremented based on the maximum value of all entity object version numbers in the BIM model. Or if one or more of the geometric data, attribute data, and relationship data of a new entity object is added, the version number of the entity object shall be incremented based on one or more of the maximum geometric data version number, the maximum attribute data version number, and the maximum relationship data version number among all version identifiers in the BIM model, and the entity object version number shall be incremented based on the maximum value of all entity object version numbers in the BIM model.

7. A BIM model version management method based on version identifier according to claim 5, characterized in that: If you delete an entity object in the BIM model, the corresponding entity object version number will be deleted and marked. Or if one or more of the geometric data, attribute data, and relationship data of the entity object is deleted, the version numbers are incremented and marked based on one or more of the maximum geometric data version number, the maximum attribute data version number, and the maximum relationship data version number among all version identifiers in the BIM model, and the entity object version number is incremented based on the maximum value of all entity object version numbers in the BIM model.

8. A BIM model version management method based on version identifier according to claim 5, characterized in that: When editing one or more of the geometric data, attribute data, and relationship data of an entity object in the BIM model, the version numbers are incremented based on one or more of the maximum geometric data version number, the maximum attribute data version number, and the maximum relationship data version number among all version identifiers in the BIM model, and the entity object version number is incremented based on the maximum value of all entity object version numbers in the BIM model.

9. A BIM model version management method based on version identifier according to claim 1, characterized in that: The step of integrating the used or edited BIM model sub-version with the BIM model main version based on the version identifier to update the BIM model main version at least includes: Obtain the BIM model sub-version processed by the application system, and compare it with the BIM model sub-version at the time of extraction and the current BIM model main version in units of entity objects, including at least geometric data, attribute data, and relationship data, so as to identify a set of entity objects with state changes; Resolve conflicts one by one for the entity object sets that have undergone state changes; The entity objects after conflict resolution are merged into the main version of the BIM model, and the version identifiers of the corresponding entity objects in the main version of the BIM model are updated.

10. A BIM model version management method based on version identifier according to claim 9, characterized in that: The obtaining of the BIM model sub-version processed by the application system is compared with the BIM model sub-version at the time of extraction and the current BIM model main version in units of entity objects, including at least geometric data, attribute data, and relationship data, so as to identify a set of entity objects with state changes, specifically including: Compare the version identifier of the updated BIM model sub-version with the version identifier of the initially extracted BIM model sub-version, and mark the status of the entity objects in the updated BIM model sub-version as one or more of unchanged, updated, added, and deleted, so as to obtain a set of entity objects in which the status of the sub-model has changed; The version identifier of the current BIM model main version is compared with the version identifier of the initially extracted BIM model sub-version, and the entity object status of the current BIM model main version is marked as one or more of unchanged, updated, deleted and added, so as to obtain a set of entity objects of the main model with status changes.

Citation Information

Cited By

  • Hierarchical multi-agent construction progress simulation method and system

    CN122452379A

  • A hierarchical multi-agent construction progress simulation method and system

    CN122452379B

  • A bim-based engineering construction progress simulation visualization method and system

    CN122818508A