Construction engineering information management method and system, electronic equipment and storage medium

By adopting the main model management method based on MBD technology in the field of construction engineering, the design problem hidden in the two-dimensional drawing delivery method and the information conflict in the BIM technology are solved, and efficient coordination and data consistency of construction engineering information are achieved, improving the The efficiency and quality of construction projects.

CN119066733APending Publication Date: 2024-12-03CHINA TRANSPORT INFORMATION TECH GRP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410937110.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-12
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In the field of construction engineering, information delivery methods based on two-dimensional drawings lead to hidden design problems, resulting in increased collaborative workload, time and cost loss, and the multi-sub-model application of BIM technology has problems with information conflicts and data integration, especially in software manufacturers. Supported data conversion is prone to loss and format conversion problems.

Method used

Using the main model management method of construction engineering information based on MBD technology, the main model management system and sub-application plug-ins are built, and the construction engineering information is stored and managed through the main data model unit, metadata management unit, data blood relationship management unit and information retrieval unit to realize the construction engineering information. Business object association relationship and metadata management, sub-application plug-ins perform data format conversion and information flow tracking, and determine data exchange standards to improve system compatibility.

Benefits of technology

It reduces the docking workload between the main model management system and the sub-application tools, improves the construction efficiency and quality of construction projects, ensures data consistency and compatibility, reduces data loss and format conversion problems, and realizes business collaboration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119066733A_ABST
    Figure CN119066733A_ABST
Patent Text Reader

Abstract

The invention discloses a construction engineering information management method and system, electronic equipment and a computer readable storage medium, and the method comprises the steps: constructing a main model management system which comprises a main data model unit, a metadata management unit, a data consanguinity management unit, a version management unit and an information retrieval unit; constructing at least one sub-application plug-in, including constructing an information flow tracking unit, a data conversion unit and an intra-domain retrieval unit; and determining a data exchange standard of information exchange between the main model management system and the sub-application plug-ins, and taking the main model management system as a data source of each sub-application and managing data. According to the method, data management is carried out between the main model management system and the sub-applications in a metadata mode, the docking workload between the main model management system and the sub-applications can be reduced, the sub-applications can cooperate based on a set of complete and consistent main model data sources, and the construction efficiency and quality of constructional engineering are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of construction engineering information technology, and in particular to a construction engineering information management method, system, electronic equipment and storage medium. Background Art

[0002] The MBD (Model-Based definition) technology in the manufacturing industry uses a unique set of product data and takes data as the core to fully express product definition information, and drives work collaboration among product design, process, simulation, processing, assembly and other businesses through changes in data.

[0003] The construction industry is different from the manufacturing industry. Two-dimensional drawings have always been the main carrier of information delivery. However, due to the limitation of the information carrying capacity of two-dimensional drawings, a large number of design problems will be hidden when the construction engineering information is transferred, which also leads to the problem that a large amount of important non-drawing information cannot be transmitted downstream. This method will not only increase the workload of collaborative work, but also be accompanied by the problem of rework of on-site engineering, resulting in a large amount of time loss and cost loss.

[0004] The construction engineering field is characterized by cross-organizational and cross-cycle collaboration. Collaboration based on two-dimensional drawings is bound to become a key bottleneck restricting the efficiency and quality of construction projects. After the introduction of BIM (Building Information Model) technology in the construction engineering field, some problems hidden in two-dimensional drawings are exposed and solved by remodeling drawings.

[0005] At present, the solution based on BIM technology in the field of construction engineering is presented as a multi-professional, multi-stage multi-sub-model BIM point application method, such as design, deepening, simulation, process, construction organization, pricing and quantity calculation, simulation, project management, etc. Although this method has improved the efficiency of single-point business to a certain extent, in terms of business collaboration, this method not only fails to fundamentally solve the upstream and downstream collaboration problems, but also has more information conflicts between sub-models due to the existence of multiple domain sub-models and the loss of reference (data lineage and version) relationships between sub-models. And the data connection method corresponding to this method is usually to use a set of physical entity data in the main model for data connection. This method requires frequent engineering information exchange between the main model management system and professional sub-applications, with large data volume and complex data structure, and needs to continuously deal with the problem of engineering format conversion. However, for most professional software, its data format is opaque, such as Autodesk's revit software, so there are generally irreversible problems such as data loss and format conversion when converting engineering data. Without the support of software manufacturers, this solution is difficult to implement. Summary of the invention

[0006] Based on the above background, the purpose of the present invention is to provide a master model of construction engineering information based on MBD technology, so that construction projects can work and collaborate based on the model, thereby improving the work efficiency and construction quality of construction projects.

[0007] To achieve the above object, the present invention adopts the following technical solutions:

[0008] In a first aspect, the present invention provides a method for managing a master model of construction engineering information, comprising:

[0009] Constructing a master model management system, including constructing a master data model unit, a metadata management unit, a data lineage management unit, a version management unit, and an information retrieval unit, and storing the association relationship of business objects in the construction engineering information based on the master data model unit, storing business object related information and metadata of sub-application engineering data based on the metadata management unit, performing data lineage management and version management on business objects based on the data lineage management unit and the version management unit, and generating and sending retrieval instructions to sub-application plug-ins based on the information retrieval unit;

[0010] Constructing at least one sub-application plug-in, including constructing an information flow tracking unit, a data conversion unit, and an intra-domain retrieval unit, wherein the sub-application plug-in is used to receive a retrieval instruction from the main model management system, retrieve the business object data based on the intra-domain retrieval unit according to the retrieval instruction, and convert the engineering data of the sub-application into a format based on the data conversion unit and then synchronize it to the main model management system; and is also used to track the business object based on the information flow tracking unit, and feed back to the main model management system when the data of the business object changes;

[0011] Determine the data exchange standard for information exchange between the main model management system and the sub-application plug-in, and use the main model management system as a data source to provide data for the sub-application.

[0012] Furthermore, the association relationship of the business objects in the construction project information stored based on the master data model unit includes:

[0013] Obtain engineering data for construction projects;

[0014] Divide the business objects in the engineering data into domains based on pre-set division rules;

[0015] Business object data is organized and stored through ER entity relationship diagrams, indicating the relationships between sub-applications and business objects.

[0016] Furthermore, the preset division rules are set according to the actual professional division of labor, and the division dimensions include the engineering model dimension and the engineering management and operation dimension;

[0017] The engineering model dimensions include the design fields of architecture, structure, and electromechanical, the analysis fields of structural analysis, thermal environment analysis, and optical link analysis, and the engineering drawing model field;

[0018] The engineering management and operation dimensions include process and method, task breakdown structure WBS, engineering quantity, pricing, procurement management, contract management, cost management and planning management business areas.

[0019] Furthermore, the metadata based on the metadata management unit storing the business object related information and the sub-application engineering data includes:

[0020] Based on the business objects recorded in the master data model unit, record the identity, object type, and sub-application information of each business object;

[0021] Based on the sub-application plug-in, the behavior data of the entire life cycle of the business objects in the sub-application is obtained and recorded in the form of metadata.

[0022] Furthermore, the data lineage management unit performs data lineage management on the business object including:

[0023] Acquire the interrelationships between business objects and between business objects and corresponding parameters in the master data model unit to build data lineage;

[0024] Track sub-application behavior data changes based on sub-application plug-ins;

[0025] When the sub-application data behavior changes, the impact scope of the business object change is confirmed through data lineage relationships;

[0026] Acquire the sub-application data of the business object stored in the metadata management unit, and determine the sub-application of the business object affected by the changed data;

[0027] Send the change information to the corresponding sub-application.

[0028] Furthermore, the generating and sending of a retrieval instruction to the sub-application plug-in based on the information retrieval unit includes:

[0029] Get the retrieval request;

[0030] Parse the search request to obtain the business object to be searched;

[0031] Determine the sub-application where the business object to be retrieved is located through the metadata management unit and generate a retrieval instruction;

[0032] Send the search instruction to the corresponding sub-application plug-in.

[0033] Furthermore, the data exchange standard for information exchange between the main model management system and the sub-application plug-in includes the IFC industry foundation class general standard and / or the GIM power grid information model standard.

[0034] In a second aspect, the present invention provides a construction engineering information master model management system, including a master model management system and a plurality of sub-application plug-ins;

[0035] The master model management system includes a master data model unit, a metadata management unit, a data lineage management unit, a version management unit and an information retrieval unit; the master data model unit is used to store the association relationship of business objects in the construction engineering information, the metadata management unit is used to store business object related information and metadata of the engineering data of the sub-application, the data lineage management unit and the version management unit are used to perform data lineage management and version management on the business objects, and the information retrieval unit is used to generate and send a retrieval instruction to the sub-application plug-in;

[0036] The sub-application plug-in includes an information flow tracking unit, a data conversion unit, and an intra-domain retrieval unit. The sub-application plug-in is used to receive a retrieval instruction from the main model management system, retrieve the information flow based on the intra-domain retrieval unit according to the retrieval instruction, and convert the engineering data of the sub-application into a format based on the data conversion unit and then synchronize it to the main model management system; it is also used to track the business object based on the information flow tracking unit, and feed back to the main model management system when the data of the business object changes;

[0037] The main model management system and the sub-application plug-in exchange information based on a preset data exchange standard, and the main model management system serves as a data source to provide data for the sub-application.

[0038] In a third aspect, the present invention provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the construction project information management method as described above when executing the computer program.

[0039] In a fourth aspect, the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned construction project information management method is implemented.

[0040] The beneficial effects of the present invention are as follows:

[0041] The present invention provides a master model management method, system, electronic device and storage medium in the field of construction engineering. The system includes a master model management system and several sub-application plug-ins. In the master model management system, a master data model unit containing business object association relationships and a metadata management unit storing engineering information in the form of metadata are constructed. The master model management system and the sub-applications use central exchange and metadata management to reduce the workload of docking between the master model management system and existing professional sub-application tools, improve the compatibility of the system, and allow application tools in various business fields to collaborate based on a complete and consistent master model data source, thereby improving the construction efficiency and quality of construction engineering.

[0042] In addition, a data lineage management unit is constructed based on the mutual relationships between business objects and between business objects and their parameters in the main data model unit. When the data behavior of a sub-application changes, the impact of the change in the business object is confirmed through the data lineage relationship. And based on the sub-application system data where the business object is located stored in the metadata management unit, the sub-application where the business object affected by the changed data is located is determined, further facilitating business collaboration among sub-applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0044] Figure 1 A schematic diagram of the main process of a construction engineering information master model management method provided by an embodiment of the present invention;

[0045] Figure 2 A schematic diagram of a framework of a construction engineering information master model management system provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0046] In order to further understand the present invention, preferred embodiments of the present invention are described below in conjunction with examples. However, it should be understood that these descriptions are only for further illustrating the features and advantages of the present invention, rather than limiting the claims of the present invention.

[0047] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used herein in the specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. The term "and / or" used herein includes any and all combinations of one or more related listed items.

[0048] It should be noted that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow charts describe the steps as sequential processes, many of the steps can be implemented in parallel, concurrently or simultaneously. In addition, the order of the steps can be rearranged. The process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0049] Example 1

[0050] See also Figure 1 This embodiment provides a construction project information management method, comprising the following steps:

[0051] S1: constructing a master model management system, including constructing a master data model unit, a metadata management unit, a data lineage management unit, a version management unit and an information retrieval unit, storing the association relationship of business objects in the construction engineering information based on the master data model unit, storing business object related information and metadata of sub-application engineering data based on the metadata management unit, performing data lineage management and version management on business objects based on the data lineage management unit and the version management unit, and generating and sending retrieval instructions to sub-application plug-ins based on the information retrieval unit;

[0052] S2: at least one sub-application plug-in, including a construction information flow tracking unit, a data conversion unit and an intra-domain retrieval unit, the sub-application plug-in is used to receive a retrieval instruction from the main model management system, retrieve the business object to be retrieved based on the intra-domain retrieval unit according to the retrieval instruction, and synchronize the engineering data of the sub-application to the main model management system after format conversion based on the data conversion unit; it is also used to track the business object based on the information flow tracking unit, and feedback to the main model management system when the data of the business object changes;

[0053] S3: Determine the data exchange standard for information exchange between the main model management system and the sub-application plug-ins, use the main model management system as the data source of each sub-application and manage the data.

[0054] This method can ensure the information interaction between the main model management system and the sub-applications, so that the main model management system has a complete and constantly updated set of engineering data metadata information of the construction project, providing a data source for each sub-application. Specifically:

[0055] The construction of the main model management system in step S1 includes:

[0056] S101: Acquire actual construction project data information, and divide the business objects in the actual construction project requirements based on preset division rules to construct a master data model unit, which stores the association relationship between business objects in the construction project information. Including,

[0057] S1011: Obtain engineering data of the construction project;

[0058] When constructing the master data model unit, it is necessary to consider the information requirements of the entire life cycle of the actual construction project. For example, in actual construction projects, there are often business requirements such as investment planning, planning and design, construction and installation, production procurement, and operation management. Each business requirement is interrelated. When establishing the master data model unit, the above business requirement information is fully included to facilitate subsequent application expansion.

[0059] S1012: Dividing the business objects in the engineering data into business areas based on a preset division rule;

[0060] The business objects are various entities and concepts related to construction projects, including building space structure tree, systems, subsystems, components, quantity items, personnel, materials, machinery, contracts, contract terms, etc.

[0061] In this embodiment, in the division of business objects based on preset division rules, the division rules are consistent with the actual professional division of labor, and the specific division includes the engineering model dimension and the engineering management and operation dimension. Among them, the engineering model dimension includes the design fields of architecture, structure, electromechanical, etc., the analysis fields of structural analysis, thermal environment analysis, optical link analysis, etc., and the engineering drawing field; the engineering management and operation dimension includes business fields such as process methods, WBS (Work Breakdown Structure, task decomposition structure), engineering quantity, pricing, procurement management, contract management, cost management and planning management. The sub-application is the application software of the professional system in each subject domain involved in the implementation of the above-mentioned construction project. In this embodiment, it is defined in correspondence with the concept of the main model management system.

[0062] In the above division, the correlation between sub-applications is reduced through low coupling and high cohesion of business domains. This method places business objects in a domain in one domain, and only a few core business objects are related to objects in other domains. In this way, when most business objects change, they only need to be processed in this application. Only when business objects with cross-domain correlations change, cross-application collaborative processing is required. For example, in the engineering model dimension, only the component business object has cross-domain correlations. When the building space structure tree and system relationships change, they only need to be processed in the sub-applications involved, and other sub-applications not involved do not need to collaborate.

[0063] S1013: Organize and store business object data through ER entity relationship diagram, indicate the relationship between each sub-application and each business object, and obtain a complete logical structure of engineering data for the entire life cycle of an actual construction project.

[0064] S102: Constructing a metadata management unit to store and back up the metadata of the business object related information and the engineering data of the sub-application, including:

[0065] Based on the business objects recorded in the master data model unit, the metadata management unit records the identity, object type, and sub-application system information of each business object; wherein the identity of each business object is a globally unique ID to locate the business object, and the object type is used to determine which type of business object defined in the master data model unit the object belongs to.

[0066] Based on the sub-application plug-in, the behavior data of the business objects in the sub-application throughout their life cycle is obtained and recorded in the form of metadata. The metadata management unit backs up the engineering information of each sub-application completely. This method transfers less data. Only the behavior information of the business objects is transferred between the sub-application plug-in and the main model management system. The data volume is small and the data standard is easy to unify.

[0067] It should be noted that the acquisition and synchronization of the addition, deletion, modification and query behavior data of the business object data throughout its life cycle is based on the sub-application plug-in constructed in step S2, that is, the sub-application business object data is tracked through the sub-application plug-in.

[0068] S103: According to the business object association relationship recorded in the master data model unit and the mutual reference relationship between the business objects and their parameters, a business object data lineage management unit and a version management unit are constructed to perform data lineage management and version management on the business objects.

[0069] The data lineage management of business objects includes:

[0070] S1031: According to the association relationship of the business objects recorded in the master data model unit, and the mutual reference relationship between the business objects and their parameters, the data lineage relationship between the business objects is constructed. For example, the volume of concrete is calculated based on the volume of the structural parts, and the geometric dimensions of the structural parts are determined based on the geological conditions and load-bearing information.

[0071] S1032: Based on the logical mapping relationship between the business object in the main data model unit and its specific expression in the sub-application, obtain and monitor whether the sub-application behavior data changes based on the sub-application plug-in;

[0072] S1033: When the sub-application data behavior changes, that is, the sub-application adds, deletes, modifies, or queries the business object, the impact scope of the business object change can be confirmed through the data lineage relationship;

[0073] S1034: Determine the sub-application where the business object affected by the changed data is located, through the sub-application data where the business object is located stored in the metadata management unit;

[0074] S1035: Notify the sub-application of the specific change content and impact scope to facilitate business collaboration between sub-applications.

[0075] The version management unit performs version management on the business object including:

[0076] Based on the engineering data recorded in the metadata management unit, the version history of each business object is recorded and managed, and the version information can be automatically recorded and compared, and the version can be rolled back according to user operations. The information of each version includes the changer, the sub-application that initiated the change, the change time, the change notes, etc.

[0077] S104: constructing an information retrieval unit for obtaining a retrieval request and generating a data retrieval instruction to send to the sub-application plug-in; including:

[0078] S1041: Obtaining the user's interactive behavior, that is, the search request; the user can perform data search of the engineering business object by means of graphic and chart interaction or by means of database search language;

[0079] S1042: Parse the search request to obtain the business object to be searched;

[0080] S1043: Determine the sub-application where the business object to be retrieved is located in combination with the sub-application information where the business object to be retrieved is located recorded by the metadata management unit and generate a search instruction; the search instruction content includes the business object to be retrieved and the sub-application where the business object to be retrieved is located determined by the metadata management unit;

[0081] S1044: Send the search instruction to the corresponding sub-application plug-in. After the sub-application plug-in executes the search instruction, the information search unit can display the data content in a graphical and chart manner and feed back the result to the user.

[0082] In step S2, constructing a sub-application plug-in to track the data flow of the business object includes:

[0083] S201: Construct an information flow tracking unit, which is used to establish a logical mapping relationship between the business objects of each professional field recorded in the main data model unit and the specific expression of each business object in the sub-application, and track the data flow of the business object based on the mapping relationship, and feedback to the main model management system when the data of the business object changes. For example: in the quantity calculation and pricing software, in the main data model unit, the business objects of engineering quantity and cost are registered, and the information flow tracking unit tracks the engineering quantity and cost data in the quantity calculation and pricing software, and synchronizes the addition, deletion, modification and query behavior of the sub-application data throughout the life cycle to the metadata management unit of the main model management system.

[0084] S202: Construct a data conversion unit, which is used to convert the data format of the sub-application into the data format agreed upon by the main model management system. Specifically, each sub-application has its own physical data organization form. When transferring data of business objects, it is necessary to convert the data format of the sub-application into the data format agreed upon by the main model management system. For example, the rvt file is a building information model (BIM) file created by the Revit software and has its own data organization form. The data conversion unit is responsible for obtaining the business object data in rvt through the SDK (Software Development Kit) opened by rvt, and converting it into the data format agreed upon by the main model management system.

[0085] S203: constructing an intra-domain retrieval unit, wherein the intra-domain retrieval unit is used to obtain a retrieval instruction and perform data retrieval on the engineering data of the sub-application according to the retrieval instruction, extract corresponding retrieval data, and complete the data retrieval action.

[0086] In step S3, the data exchange standard for information exchange between the main model management system and the sub-application plug-in is determined, and the main model management system is used as a data source to provide data for the sub-application, including:

[0087] S301: Through the investigation of construction engineering projects, determine the professional application software used by each business participant, that is, sub-applications, such as software applications in the fields of design, deepening, simulation, process, construction organization, pricing and quantity calculation, simulation, project management, etc., and determine the data format of the corresponding software;

[0088] S302: Determine the data exchange standard for information exchange between the main model management system and the sub-application to ensure information exchange between the main model management system and the sub-application;

[0089] The sub-application engineering data is the professional engineering data in each professional software. When the main model management system performs data retrieval, the main model management system and the sub-application exchange data of the engineering object.

[0090] The data exchange standard can use general standards, such as IFC, Industry Foundation Classes, which is an industry foundation class that provides an open format for information exchange in the construction industry. General standards can greatly reduce the workload of standard formulation and development. Other standards can also be selected or established according to actual needs, such as GIM (Grid Information Model), which defines a set of data exchange standards for the power grid industry.

[0091] S303: Using the main model management system as the data source for each sub-application;

[0092] As each sub-application repeatedly uses, processes, revises, and superimposes the main data model unit, and synchronizes the sub-application's engineering data to the metadata management unit in the form of metadata through the sub-application plug-in, the main model management system has a complete set of engineering data metadata information that is continuously updated with the business process, providing a data source for each sub-application. On this basis, the data lineage unit and version management unit in the main model management system ensure that the data in the main model management system is consistent.

[0093] It should be noted that the main model management system does not have a complete set of data, but only has metadata information of a complete set of data. According to specific needs, the metadata management unit can extract the corresponding data information in the sub-application and hand it over to the demander in a certain standard data format. This method can reduce the frequency and amount of data exchange between the main model management system and the sub-application.

[0094] The master model management system constructed by the embodiment of the present invention integrates the information of the key business objects of each sub-application, and establishes the correct version and information reference of the global data through the master model management system based on the information of each sub-application. The master model management system has the characteristics of complete information and consistent data. In practical applications, the master model management system is used as the core to provide a unique data source for the construction project, which allows the sub-applications in various business fields to collaborate based on a complete and consistent master model data source, thereby improving the construction efficiency and quality of the construction project.

[0095] Example 2

[0096] See also Figure 2 This embodiment provides a construction engineering information management system based on MBD technology, including a main model management system and several sub-application plug-ins. The sub-application plug-ins are used to obtain the engineering data of the sub-applications in the corresponding subject domain and synchronize them to the main model management system in the form of metadata. The main model management system manages the construction engineering information. As the sub-applications repeatedly access, process, revise, and overlay the data in the main model management system, and the data after the sub-application operations are synchronized to the main model management system, the main model management system has a complete and continuously updated set of metadata information of engineering data, providing a data source for the construction engineering project.

[0097] Specifically:

[0098] The main model management system includes a main data model unit, a metadata management unit, a data lineage management unit, a version management unit and an information retrieval unit.

[0099] The master data model unit is used to obtain the engineering data of the construction project, establish the logical structure of the engineering data of the entire life cycle of the construction project, indicate the association relationship between each sub-application and each business object, and provide a basis for the metadata management unit, the data lineage management unit and the version management unit to perform data operations;

[0100] The metadata management unit is used to record the identity, object type, sub-application system, and even the addition, deletion, modification, and query behaviors of each business object in the main data model unit throughout the data life cycle.

[0101] The data lineage management unit determines the impact scope of a data change based on the data association relationship between business objects indicated by the main data model unit after a business object data changes, and informs the corresponding sub-application to perform a data update operation.

[0102] The version management unit records and manages the version history established for each business object based on the engineering data recorded in the metadata management unit, can perform automated version comparison and record each version information, and can perform version rollback according to user operations.

[0103] The information retrieval unit is used to obtain a retrieval request and generate a corresponding data retrieval instruction; specifically, the retrieval request is parsed to obtain the object to be retrieved, the sub-application where the business object to be retrieved is located is determined through the sub-application data where the business object is located recorded in the metadata management unit, and the corresponding retrieval instruction is generated. It can display data content in a graphical and chart manner, and can also perform data retrieval of engineering objects in a graphical and chart interactive manner or in a database retrieval language manner.

[0104] The main model management system establishes a complete set of data logic structures between each sub-application, determines the data association and data mapping relationship between the main data model unit and each sub-application, and meets the retrieval needs of engineering data through the information retrieval unit.

[0105] The sub-application plug-in includes an intra-domain retrieval unit, a data conversion unit, and an information flow tracking unit.

[0106] The intra-domain retrieval unit is used to receive data retrieval instructions from the information retrieval unit in the main model management system. The retrieval instruction content includes the business object to be retrieved and the sub-application where the business object is located as determined by the metadata management unit. The intra-domain retrieval unit executes the retrieval task, extracts the corresponding retrieval data, and completes the data retrieval action.

[0107] The data conversion unit converts the data format of each sub-application into the data format agreed upon by the main model management system when transferring business object data according to the physical data organization form of each sub-application.

[0108] The information flow tracking unit is used to track the corresponding business objects according to the registration content in the main data model unit, and feed back to the main model management system when the data of the business objects changes.

[0109] The main model management system and the sub-application plug-in exchange information based on a preset data exchange standard, and the main model management system serves as a data source to provide data for the sub-application.

[0110] In summary, the sub-application plug-in is the specific executor of engineering object data management, and is responsible for dynamically synchronizing the engineering object data of this profession to the main model management system. Specifically, when the information retrieval unit of the main model management system generates a data retrieval instruction, the domain retrieval unit of the sub-application plug-in executes the data retrieval instruction to retrieve and extract the data, and submits the extracted data results to the main model management system through the data conversion unit.

[0111] Example 3

[0112] This embodiment provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the construction project information management method described in the above-mentioned embodiment 1 is implemented.

[0113] Example 4

[0114] An embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the construction project information management method described in the above-mentioned embodiment 1 is implemented.

[0115] The above embodiments are only used to help understand the method and core idea of ​​the present invention. It should be noted that, for those skilled in the art, several improvements and modifications can be made to the present invention without departing from the principles of the present invention, and these improvements and modifications also fall within the scope of protection of the claims of the present invention.

Claims

1. A construction engineering information management method, characterized in that: include, Constructing a master model management system, including constructing a master data model unit, a metadata management unit, a data lineage management unit, a version management unit, and an information retrieval unit, and storing the association relationship of business objects in the construction engineering information based on the master data model unit, storing business object related information and metadata of sub-application engineering data based on the metadata management unit, performing data lineage management and version management on business objects based on the data lineage management unit and the version management unit, and generating and sending retrieval instructions to sub-application plug-ins based on the information retrieval unit; Constructing at least one sub-application plug-in, including constructing an information flow tracking unit, a data conversion unit, and an intra-domain retrieval unit, wherein the sub-application plug-in is used to receive a retrieval instruction from the main model management system, retrieve the business object data based on the intra-domain retrieval unit according to the retrieval instruction, and convert the engineering data of the sub-application into a format based on the data conversion unit and then synchronize it to the main model management system; and is also used to track the business object based on the information flow tracking unit, and feed back to the main model management system when the data of the business object changes; Determine the data exchange standard for information exchange between the main model management system and the sub-application plug-in, and use the main model management system as a data source to provide data for the sub-application.

2. The construction engineering information management method according to claim 1, characterized in that: The association relationship of business objects in the construction project information stored based on the master data model unit includes: Obtain engineering data for construction projects; Divide the business objects in the engineering data into domains based on pre-set division rules; Business object data is organized and stored through ER entity relationship diagrams, indicating the relationships between sub-applications and business objects.

3. The construction engineering information management method according to claim 2, characterized in that: The preset division rules are set according to the actual professional division of labor, and the division dimensions include the engineering model dimension and the engineering management and operation dimension; The engineering model dimensions include the design fields of architecture, structure, and electromechanical, the analysis fields of structural analysis, thermal environment analysis, and optical link analysis, and the engineering drawing model field; The engineering management and operation dimensions include process and method, task breakdown structure WBS, engineering quantity, pricing, procurement management, contract management, cost management and planning management business areas.

4. The construction engineering information management method according to claim 1, characterized in that: The metadata based on the metadata management unit storing the business object related information and the sub-application engineering data includes: Based on the business objects recorded in the master data model unit, record the identity, object type, and sub-application information of each business object; Based on the sub-application plug-in, the behavior data of the entire life cycle of the business objects in the sub-application is obtained and recorded in the form of metadata.

5. The construction engineering information management method according to claim 1, characterized in that: The data lineage management unit performs data lineage management on the business object including: Acquire the interrelationships between business objects and between business objects and corresponding parameters in the master data model unit to build data lineage; Track sub-application behavior data changes based on sub-application plug-ins; When the sub-application data behavior changes, the impact scope of the business object change is confirmed through data lineage relationships; Acquire the sub-application data of the business object stored in the metadata management unit, and determine the sub-application of the business object affected by the changed data; Send the change information to the corresponding sub-application.

6. The construction engineering information management method according to claim 1, characterized in that: The generating and sending of the retrieval instruction based on the information retrieval unit to the sub-application plug-in includes: Get the retrieval request; Parse the search request to obtain the business object to be searched; Determine the sub-application where the business object to be retrieved is located through the metadata management unit and generate a retrieval instruction; Send the search instruction to the corresponding sub-application plug-in.

7. The construction engineering information management method according to claim 1, characterized in that: The data exchange standard for information exchange between the main model management system and the sub-application plug-in includes the IFC industry foundation class general standard and / or the GIM power grid information model standard.

8. A construction project information management system, characterized in that: Includes the main model management system and several sub-application plug-ins; The master model management system includes a master data model unit, a metadata management unit, a data lineage management unit, a version management unit and an information retrieval unit; The master data model unit is used to store the association relationship of business objects in the construction project information, the metadata management unit is used to store the business object related information and the metadata of the sub-application project data, the data lineage management unit and the version management unit are used to perform data lineage management and version management on the business objects, and the information retrieval unit is used to generate and send a retrieval instruction to the sub-application plug-in; The sub-application plug-in includes an information flow tracking unit, a data conversion unit, and an intra-domain retrieval unit. The sub-application plug-in is used to receive a retrieval instruction from the main model management system, retrieve the information flow based on the intra-domain retrieval unit according to the retrieval instruction, and convert the engineering data of the sub-application into a format based on the data conversion unit and then synchronize it to the main model management system; it is also used to track the business object based on the information flow tracking unit, and feed back to the main model management system when the data of the business object changes; The main model management system and the sub-application plug-in exchange information based on a preset data exchange standard, and the main model management system serves as a data source to provide data for the sub-application.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the construction project information management method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the construction project information management method according to any one of claims 1 to 7 is implemented.