A smart building engineering management system based on a BIM platform

Abstract

This invention provides a smart building engineering management system based on a BIM platform, belonging to the field of building engineering information management technology. It includes: a model processing module for parsing the BIM model, obtaining the geometric and attribute information of each component, and generating a unique permanent component identifier for each component based on the geometric and attribute information; and a version mapping module. This invention generates a permanent component identifier based on the component's geometric and attribute information, and uses this identifier, rather than the component identifier inherent in the model file, as the association key for business data. Simultaneously, through spatial matching and attribute matching, it automatically establishes one-to-one, one-to-many, and many-to-one inheritance mapping relationships between components before and after model upgrades. This ensures that business data can be automatically continued to the new version of components even in the event of design changes, component splitting, or merging. This fundamentally solves the problem of business data disconnection caused by model upgrades in existing technologies, eliminating the need for manual re-attaching and ensuring the complete preservation of the component's entire process archive.

Description

Technical Field

[0001] This invention relates to the field of information management technology for building engineering, and in particular to a smart building engineering management system based on a BIM platform. Background Technology

[0002] Building Information Modeling (BIM) uses three-dimensional digital models to represent the geometric and attribute information of building components. It is currently widely used in clash detection and quantity surveying during the design phase. With the advancement of smart construction site development, the engineering construction industry hopes to extend the application of BIM models to the construction phase, enabling on-site business data such as progress, quality, materials, and personnel to be stored at the component level, forming searchable and traceable engineering data assets.

[0003] However, most existing BIM construction management systems only use the BIM model as a display medium, while on-site business data is still stored in the project management software in the form of independent forms and photos. There is a lack of stable and reliable correlation between the two, which specifically presents the following problems: First, the efficiency of associating on-site business data with components is low. Existing systems typically require operators to expand the model tree level by level on mobile terminals, or repeatedly rotate and zoom in a 3D view before selecting components to complete the association between business data and components. A medium-sized building construction project often has hundreds of thousands of components, and the hierarchy of floors, specialties, and component types is quite deep. This makes it difficult for operators to operate in on-site environments such as scaffolding and formwork work surfaces. Each association takes a long time and is very easy to mistakenly attach to adjacent components.

[0004] Second, model upgrades lead to data silos in business processes. Frequent design changes during construction necessitate multiple BIM model upgrades. During these upgrades, components may be deleted and recreated, split into multiple components, or merged into a single component, changing their component identifiers in the model file (e.g., GlobalId in IFC format). Since the existing system directly uses the component identifiers from the model file as the association keys for business data, once the model is upgraded, previously attached business data such as inspection batch records, concealed works images, and material batches lose their correspondence with the components in the new model, creating data silos. Restoring these associations requires manual comparison of the old and new models and reattaching them, a massive undertaking prone to errors and prone to omissions, resulting in incomplete and untraceable component documentation throughout the entire process.

[0005] Third, the progress data is distorted; the existing system's visual progress mainly relies on managers manually filling in the percentage of completion by floor or section, which is highly subjective and disconnected from the quality acceptance data. This can easily lead to situations where previous processes are not yet accepted and are reported as completed, and the progress data cannot objectively reflect the actual situation on site.

[0006] Fourth, the closed-loop management of quality issues and the traceability of responsibility are difficult; quality issue reports often only record the description of the floor and part, without being strongly linked to specific components, process nodes and responsible persons, and the rectification closed loop relies on manual tracking; when defects occur after the project is delivered, it is difficult to quickly trace back to the construction records, material batches and work teams of that part.

[0007] Therefore, it is evident that maintaining the continuous correlation between on-site business data and components under the condition of multiple BIM model upgrades, while reducing the operational difficulty of on-site data correlation and achieving objective judgment of construction progress, is a technical problem that urgently needs to be solved in this field. Summary of the Invention

[0008] The purpose of this invention is to provide a smart building engineering management system based on a BIM platform to solve the problems of broken business data links, low correlation efficiency, and distorted progress data.

[0009] To solve the above-mentioned technical problems, the present invention adopts the following technical solution: A smart building engineering management system based on a BIM platform includes: The model processing module is used to parse the BIM model, obtain the geometric and attribute information of each component, and generate a unique permanent component identifier for each component based on the geometric and attribute information. The version mapping module is used to establish an inheritance mapping relationship based on the geometric and attribute information of components before and after the upgrade when the BIM model is upgraded, and to assign the permanent component identifier of the component before the upgrade to the upgraded component with the inheritance mapping relationship. The field acquisition module is used to acquire the location information of the field terminal and return the candidate components located within the range indicated by the location information to the field terminal. The data association module is used to store business data uploaded by field terminals, using the permanent identifier of the selected candidate component as an index. The progress engine module is used to update the process status of a component when its business data meets the preset process completion conditions, and drive the display of the BIM model according to the updated process status.

[0010] Preferably, the model processing module includes an identifier generation unit; The identifier generation unit is used to extract the coordinates of the center point of the outer bounding box of the component in the project base point coordinate system, the floor to which the component belongs, the professional type and the component type, and then encodes the extracted results and splices them to generate a permanent identifier for the component. The permanent component identifiers and the component identifiers that come with the BIM model are stored separately and independently.

[0011] Preferably, the version mapping module includes: The spatial matching unit is used to search for components in the upgraded components whose center point distance is less than a first threshold and whose overlap volume with the outer bounding box is greater than a first proportion, based on the outer bounding box of the component before the upgrade, to obtain a candidate mapping set. The attribute matching unit is used to perform attribute verification on the components in the candidate mapping set and remove components whose component type, professional type, floor or material grade is inconsistent with the components before the upgrade. The relationship determination unit is used to determine whether the inheritance mapping relationship is one-to-one, one-to-many, or many-to-one based on the number of components in the verified candidate mapping set and their correspondence with the components before the upgrade.

[0012] Preferably, the version mapping module further includes a data inheritance unit, which is used for: When the inheritance mapping relationship is one-to-one, the business data of the component permanent identifier and its index of the component before the upgrade will be assigned to the component after the upgrade. When the inheritance mapping relationship is one-to-many, the permanent component identifier of the component before the upgrade is assigned to the component with the largest volume after the upgrade, and the lower-level identifiers derived from the permanent component identifier are assigned to the remaining components after the upgrade. The business data is then attached to the components after the upgrade according to the location of the business data collection. When the inheritance mapping relationship is many-to-one, the business data of each component index before the upgrade will be attached to the upgraded component, and the source identifier of the business data will be retained. Furthermore, if the relationship determination unit fails to determine the inheritance mapping relationship, the corresponding component is written into the confirmation queue, and the inheritance mapping relationship is written back after receiving the confirmation instruction.

[0013] Preferably, the version mapping module also includes a change trace unit, which is used to record the inheritance mapping relationship, mapping type, effective version number and operation time of each version upgrade, and restore the association relationship between components and business data according to the specified version number when a backtracking instruction is received.

[0014] Preferably, the field data acquisition module includes: The positioning unit is used to receive the location code obtained by the field terminal scanning the positioning tag, or to receive the beacon signal collected by the field terminal, so as to obtain the floor and plane position of the field terminal. The candidate filtering unit is used to form a filtering area based on the planar position, according to a set radius and a set horizontal orientation angle range. It retrieves the components located within the filtering area from the spatial index stored in blocks according to floors and axis grids, and returns them in order of distance from the planar position from near to far. The data acquisition unit is used to receive business data uploaded by field terminals. The business data includes process node codes, image files, acceptance conclusions, and operator identification.

[0015] Preferably, the field acquisition module also includes an offline caching unit, which is used to temporarily store business data and the permanent identifier of the selected candidate components locally on the field terminal when the field terminal is disconnected from the server, and upload them in the order of temporary storage after the connection is restored. The data association module is also used to retain the data with the larger model version number when multiple business data entries exist under the same permanent identifier of the same component.

[0016] Preferably, the progress engine module includes: The state machine unit is used to configure the sequence of process nodes according to the component type and to configure the process completion conditions for each process node. The process completion conditions include that the necessary business data of the process node is complete and the acceptance conclusion is qualified. The status advancement unit is used to set the process node as completed when the process node of the component meets the process completion conditions, and to suspend advancement and output a process reversal alarm when the preceding process node of the process node is not completed. The display driving unit is used to assign different display states to the corresponding components in the BIM model according to the current process status of the components, and to count the amount of work completed by floor or flow section.

[0017] Preferred options also include: The quality closed-loop module is used to generate problem forms that are bound with permanent component identifiers, process node codes and responsible person identifiers. After receiving a rectification response, it triggers a re-inspection and outputs an upgrade warning if the re-inspection fails to pass the rectification deadline. The traceability module is used to bind the batch information of incoming materials with the permanent identification of components, generate a component QR code corresponding to the permanent identification of the component, and output the version change record, process record, material batch information and image file of the corresponding component when the component QR code is scanned.

[0018] A method for applying a BIM-based intelligent building engineering management system, characterized by comprising: Analyze the BIM model and generate a unique permanent identifier for each component based on its geometric and attribute information; When upgrading a BIM model, an inheritance mapping relationship is established based on the geometric and attribute information of the components before and after the upgrade, and the business data of the permanent component identifier and its index of the components before the upgrade are assigned to the upgraded components with the inheritance mapping relationship. Obtain the location information of the field terminal, return the candidate components within the range indicated by the location information to the field terminal, and store the business data uploaded by the field terminal using the permanent component identifier of the selected candidate component as an index; When the business data of a component meets the preset process completion conditions, the process status of the component is updated, and the display of the BIM model is driven according to the updated process status.

[0019] The beneficial effects of this invention are: 1. This invention generates a permanent identifier for a component based on its geometric and attribute information. This identifier, rather than the component identifier inherent in the model file, is used as the association key for business data. Simultaneously, through spatial and attribute matching, it automatically establishes one-to-one, one-to-many, and many-to-one inheritance mapping relationships between components before and after the model upgrade. This ensures that business data can be automatically continued to the new version of the component even after design changes, component splitting, and merging. This fundamentally solves the problem of business data disconnection caused by model upgrades in the prior art. No manual re-attaching is required, and the entire process file of the component is completely preserved.

[0020] 2. Based on the positioning information of the on-site terminal, this invention combines spatial indexing divided by floor and axis grid to converge the hundreds of thousands of components faced by the operator into a dozen or so candidate components in front of them. This transforms the data association from multiple operations of expanding the model tree level by level into a single point selection, significantly reducing the difficulty of on-site operation and the probability of mis-hanging.

[0021] 3. This invention uses whether the business data collected on-site meets the conditions for process completion as the basis for process status advancement, and outputs a process reversal alarm when the preceding process is not completed, so that the visual progress is transformed from manual reporting to data-driven objective judgment, avoiding unverified progress and false progress reporting.

[0022] 4. Since business data is always indexed by the permanent identifier of the component, and the mapping relationship of each version upgrade is recorded, this invention can trace back the version change record, process record, material batch and operator by component after the project is delivered, so as to realize the full-process traceability of project quality. Attached Figure Description

[0023] Figure 1 A structural block diagram of a smart building engineering management system based on a BIM platform provided in an embodiment of the present invention; Figure 2 This is a schematic diagram illustrating the process of establishing component inheritance mapping relationships when upgrading a BIM model, as provided in an embodiment of the present invention. Detailed Implementation

[0024] To facilitate understanding of the present invention, a more complete description will be given below with reference to the accompanying drawings. Preferred embodiments of the invention are shown in the drawings. However, the invention can be implemented in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided to provide a thorough and complete understanding of the disclosure of the invention.

[0025] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. The terminology used herein in the description of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.

[0026] Specific embodiments of the present invention are described below with reference to the accompanying drawings.

[0027] Example 1 This embodiment provides a smart building engineering management system based on a BIM platform, such as... Figure 1 As shown, the system includes a model processing module 100, a version mapping module 200, a field acquisition module 300, a data association module 400, a progress engine module 500, a quality closed-loop module 600, a traceability module 700, a visualization module 800, and a data storage module 900.

[0028] In terms of deployment, the model processing module 100, version mapping module 200, data association module 400, progress engine module 500, quality closed-loop module 600, traceability module 700, and data storage module 900 are deployed on the server of the project department or enterprise. The server can be a general application server, on which a relational database is used to store structured data, and an object storage service is used to store attachment files such as images. The data acquisition and positioning functions of the field acquisition module 300 are realized by an application installed on the field mobile terminal in conjunction with the server. The field mobile terminal can be a smartphone or an industrial handheld terminal, which communicates with the server through the field wireless LAN or mobile communication network. The visualization module 800's display interface runs on a browser, the project department's large screen, and mobile terminals.

[0029] The above deployment method is an example. Those skilled in the art can deploy each module on the same server or in a cluster of several servers, depending on the project scale.

[0030] The model processing module 100 includes a model parsing unit 110, a lightweighting unit 120, and an identifier generation unit 130.

[0031] Model parsing unit 110 receives the BIM model delivered by the design unit and parses out the geometric and attribute information of each component. For models in various native formats, they are first exported to IFC format before being integrated. Geometric information includes the minimum, maximum, and center point coordinates of the component's bounding box in the project base point coordinate system, as well as the component's volume; attribute information includes component type (e.g., shear wall, frame column, beam, cast-in-place slab, masonry wall, air duct, etc.), professional type (civil engineering, mechanical and electrical, decoration), affiliated unit project and floor, grid positioning number, material grade (e.g., concrete strength grade C35), and quantity.

[0032] The lightweight unit 120 is used to thin the triangular facets of the model and instantiate similar components. It also establishes spatial indexes for components according to the hierarchical levels of unit project, floor, and grid, generating a lightweight model that can be loaded in blocks. This enables browsers and mobile terminals to quickly load the model under on-site network conditions and supports quick retrieval of components by spatial range.

[0033] The identifier generation unit 130 is used to generate a unique permanent identifier for each component. The permanent identifier is composed of the project code, unit project code, floor code, professional type code, component type code, and spatial code concatenated in sequence. The spatial code is obtained by performing a digest operation on a string formed by rounding the three coordinate values ​​of the component's outer bounding box center point in the project's base point coordinate system to the nearest millimeter, and then extracting the first few characters of the digest result. For example, if a project code is P00126, the unit project code is 01, the floor code for five floors above ground is F05, the civil engineering professional code is CE, and the component type code for cast-in-place slabs is SLB, its permanent identifier would be in the form of P00126-01-F05-CE-SLB-3F9A2C7B41D6E058.

[0034] Since the project's base point coordinate system remains unchanged throughout the project, as long as the spatial location, floor, professional type, and component type of a component remain the same, its permanent component identifier will not change with the re-export of the model file or the deletion and reconstruction of the component. For situations where multiple components exist at the same location (e.g., precast and cast-in-place layers of a composite slab), their permanent component identifiers will still be different due to their different component type codes; if duplicates still occur, two sequential digits will be added at the end for differentiation.

[0035] The permanent component identifier and the component identifier that comes with the model file are stored in different fields of the component master data table, and the two are independent of each other: the component identifier that comes with the model file is only used to locate geometric objects in the current version of the model, while the permanent component identifier serves as the unique association key for business data, so that business data no longer depends on the version of the model file.

[0036] Version mapping module 200 includes spatial matching unit 210, attribute matching unit 220, relationship determination unit 230, data inheritance unit 240, and change tracking unit 250. It is used to establish inheritance mapping relationships between components before and after the BIM model upgrade. Its processing flow is as follows: Figure 2 As shown, it includes the following steps: In step S101, the model parsing unit 110 parses the upgraded BIM model and extracts the geometric and attribute information of each component.

[0037] In step S102, the spatial matching unit 210 uses the outer bounding box of the component before the upgrade as a reference to search for components in the upgraded components whose center point distance is less than a first threshold and whose overlap volume with the outer bounding box is greater than a first proportion, thus obtaining a candidate mapping set. In this embodiment, the first threshold is configured according to the component type: 50 mm for civil engineering components such as walls, columns, beams, and slabs, and 100 mm for electromechanical pipelines and equipment; the first proportion is 80%, meaning that the volume of the overlapping part of the outer bounding boxes of two components accounts for no less than 80% of the smaller of their volumes. During the search, the search range is first narrowed down by floor and grid, and then compared one by one within each block to ensure processing efficiency for hundreds of thousands of components.

[0038] In step S103, the attribute matching unit 220 performs attribute verification on the components in the candidate mapping set and removes components whose component type, professional type, floor or material grade are inconsistent with the components before the upgrade from the candidate mapping set.

[0039] In step S104, the relationship determination unit 230 determines the type of inheritance mapping relationship based on the number of components in the verified candidate mapping set and their correspondence with the components before the upgrade. The specific determination rules are as follows: If there is only one component in the candidate mapping set, and the engineering quantity deviation between the component and the component before the upgrade does not exceed 10%, it is determined to be a one-to-one mapping. If there are two or more components in the candidate mapping set, and the overlap volume of the union of the bounding boxes of these components and the bounding box of the component before the upgrade is not less than the second ratio of the volume of the component before the upgrade, then it is determined to be one-to-many, that is, one component before the upgrade is split into multiple components after the upgrade. In this embodiment, the second ratio is 85%. If the same component after the upgrade is simultaneously detected by two or more components before the upgrade, and the overlap volume ratio between the union of the bounding boxes of the components before the upgrade and the bounding box of the component after the upgrade is not less than the second ratio, it is determined to be many-to-one, that is, multiple components before the upgrade are merged into one component after the upgrade. If none of the above conditions are met, it is determined that a new component has been added or a component has been deleted, and the process proceeds to step S108.

[0040] Step S105: The data inheritance unit 240 assigns the permanent component identifier of the component before the upgrade to the component after the upgrade according to the determined mapping type, specifically as follows: When the mapping type is one-to-one, the upgraded component directly inherits the permanent component identifier of the component before the upgrade; When the mapping type is one-to-many, the component with the largest volume after the upgrade inherits the component permanent identifier of the component before the upgrade and becomes the main component. The remaining upgraded components are assigned a lower-level identifier derived from the component permanent identifier. The lower-level identifier is the component permanent identifier of the main component with two sequence numbers appended to it, and its parent component permanent identifier is recorded in the component master data table. When the mapping type is many-to-one, the component after the upgrade inherits the permanent identifier of the component with the largest volume among all components before the upgrade. The permanent identifiers of the other components before the upgrade are mapped to the permanent identifier of the component as aliases. After that, the component can also be found by querying by alias.

[0041] In step S106, the data inheritance unit 240 inherits and attaches the business data to the corresponding upgraded component according to the collection location. Each piece of business data collected on-site records the planar position at the time of collection, which is provided by the positioning unit 310 described later. When the mapping type is one-to-one, all business data is inherited along with the permanent identifier of the component; when the mapping type is one-to-many, business data whose collection location falls within the horizontal projection range of the outer bounding box of a certain upgraded component is attached to that component, and business data whose collection location is not recorded or whose collection location falls within the projection range of multiple components is attached to the main component, and its inheritance source and version number before inheritance are marked; when the mapping type is many-to-one, all business data indexed by each component before the upgrade are attached to the upgraded component, and the source identifier of each piece of business data is retained.

[0042] In step S107, the change tracking unit 250 records the inheritance mapping relationship, mapping type, effective version number, and operation time of this upgrade, and publishes the upgraded component master data. The mapping relationship table includes fields such as: permanent component identifier before the upgrade, component identifier in the model after the upgrade, mapping type, judgment criteria, effective version number, operation time, and operator. When an administrator issues a rollback instruction and specifies a version number, the change tracking unit 250 reverse-engineers the association between components and business data under that version according to the mapping relationship table, thus allowing viewing of the model and business data for any historical version.

[0043] Step S108: Components whose inheritance mapping relationship has not been determined are added to the confirmation queue. The confirmation queue is presented as a comparison view of the old and new version models on the web page of the visualization module 800. After the administrator selects the correspondence between the pre-upgrade and post-upgrade components in the comparison view, the confirmation result is written back to the mapping table, triggering the inheritance processing in steps S105 and S106. In actual projects, after adopting the above determination rules, the number of components entering the confirmation queue usually does not exceed five percent of the total number of components involved in this upgrade.

[0044] The on-site data acquisition module 300 includes a positioning unit 310, a candidate filtering unit 320, a data acquisition unit 330, and an offline caching unit 340.

[0045] The positioning unit 310 is used to obtain the floor and planar position of the field terminal. This embodiment uses positioning tags, where positioning QR codes are affixed to the entrances / exits of each floor, the core tube, and the sides of the frame columns of each flow section, with a spacing of 15 to 20 meters. The positioning QR codes contain the project code, floor code, grid section code, and the planar coordinates of the tag point in the project's base point coordinate system. Workers can obtain their floor and planar position by scanning the positioning QR code with the field terminal. Alternatively, Bluetooth beacons can be deployed at the above locations. The field terminal receives the beacon's broadcast number, which is then converted into planar coordinates by the server. In this method, the positioning error is no more than three meters. Furthermore, the positioning unit 310 reads data from the field terminal's built-in gyroscope and magnetometer to obtain the field terminal's horizontal orientation angle.

[0046] The candidate screening unit 320 is used to form a screening area with a radius of 15 meters and a sector of ±45 degrees centered on the horizontal orientation angle, using the planar position obtained by the positioning unit 310 as the vertex. The radius can be configured between 5 and 30 meters according to the site conditions. Within this screening area, the candidate screening unit 320 superimposes floor filtering conditions and professional filtering conditions, retrieves components from the spatial index established by the lightweight unit 120, sorts the components from near to far in terms of their distance from the planar position, and returns no more than 20 candidate components. The on-site terminal displays the candidate components in a list and a 3D highlighted dual view. The operator can complete the association between business data and components with a single click. For prefabricated components, a component QR code corresponding to the component's permanent identifier is assigned during the factory production stage. Scanning the component QR code on-site can directly and accurately associate the component without having to select from the candidate components.

[0047] The acquisition unit 330 is used to receive business data uploaded by the field terminal. After the operator selects a component, the field terminal automatically loads the corresponding acquisition form according to the current process node of the component. The acquisition content includes the process node code, image file, acceptance conclusion, operator identification and work group. When the image file is captured, the shooting time, acquisition location and the permanent component identification of the selected component are automatically written into it as the image watermark and metadata to ensure that the correspondence between the image and the component and time cannot be tampered with.

[0048] The offline caching unit 340 ensures no data loss when the field terminal loses connection with the server. In areas without network coverage, such as basements and elevator shafts, the field terminal temporarily stores business data and the permanent identifier of the selected component in a local embedded database and file directory, forming an upload queue. After the network is restored, the data is automatically uploaded in the order of temporary storage, and the upload process supports resuming interrupted uploads. Since the business data is bound to the permanent identifier of the component when it is temporarily stored locally, it is not affected by whether the model is upgraded during this period.

[0049] The data association module 400 uses the permanent identifier of the selected candidate component as a foreign key to write business data into a business data table. The fields of the business data table include: document number, permanent component identifier, process node code, business type, collection time, collection location, operator identifier, attachment storage address, and model version number at the time of collection. When multiple business data entries with the same collection time exist under the same permanent component identifier (e.g., duplicate data generated from offline re-upload and online submission), the data association module 400 retains the one with the larger model version number, and the other is converted to historical records and retained without deletion.

[0050] The progress engine module 500 includes a state machine unit 510, a state advancement unit 520, and a display driver unit 530.

[0051] State machine unit 510 is used to configure the sequence of process nodes according to component type and to configure the completion conditions for each process node. For example, the sequence of process nodes for cast-in-place concrete wall and column components is as follows: surveying and setting out, rebar tying, concealed rebar acceptance, formwork installation, formwork acceptance, concrete pouring, formwork removal and curing, and solid strength testing. The completion conditions for the concrete pouring node are: all necessary business data for this node are complete, namely, the pouring order, at least three images of the pouring process, and test block retention records have all been uploaded, and the acceptance conclusion for this node is qualified. The sequence of process nodes and the completion conditions can be configured by project managers in the background according to the construction organization design.

[0052] The status advancement unit 520 is used to mark a process node as completed and advance the process status of the component to the next node when a certain process node of the component meets the process completion conditions. When the preceding process node of the process node corresponding to the received business data has not yet been completed, the status advancement unit 520 temporarily suspends the advancement of the process status of the component and outputs a process reversal alarm, which is pushed to the quality inspector and production manager. The process will be advanced again after the preceding process is completed and accepted. When all process nodes of the component have been completed, the process status of the component is marked as completed.

[0053] The display driving unit 530 is used to assign different display states to the corresponding components in the BIM model according to the current process status of the components. In this embodiment, components that have not started are displayed in gray, components that are in progress are displayed in yellow, components that have been completed are displayed in green, and components with unclosed quality problems are displayed in red. At the same time, the engineering quantity of completed components is summarized by floor or flow section, and the progress deviation is output after comparing it with the four-dimensional progress plan.

[0054] The quality closed-loop module 600 generates problem orders, which are bound to a permanent component identifier, process node code, responsible person identifier, and rectification deadline. Upon receiving a rectification response, a re-inspection is triggered, requiring the upload of an image of the rectified component. Once the re-inspection is passed, the problem order is closed. If the re-inspection fails by the deadline, the quality closed-loop module 600 outputs an escalation warning to the project manager and notifies the display driver unit 530 to display the component in red. When the same component repeatedly exhibits the same type of quality problem within a set period and reaches a set number of occurrences, the quality closed-loop module 600 automatically generates a special inspection task.

[0055] The traceability module 700 is used to bind the material arrival batch information with the permanent identification of the components. The material arrival batch information includes the batch number, manufacturer, certificate number, and witnessed sampling and retesting report number. The traceability module 700 generates a component QR code corresponding to its permanent identification for each component. For cast-in-place components, this code is affixed to the surface of the component as a nameplate after completion, while for precast components, it is pre-embedded during the factory production stage. When the component QR code is scanned, the traceability module 700 outputs the component's version change record, records and images of each process node, material batch information, and information on the work team and acceptance personnel.

[0056] The visualization module 800 is used to load lightweight models on browsers, project department screens, and mobile terminals, and display them with color according to process status. It also provides comparison views of old and new model versions, visual progress boards, and quality issue boards. The data storage module 900 is used to store structured data such as component master data tables, mapping relationship tables, business data tables, process status tables, and material batch tables, as well as attachment files such as images, and interacts with the above modules.

[0057] Example 2 This example uses a commercial complex project to illustrate the process of inheriting business data during model upgrades. The project has 28 floors above ground and 3 floors below ground. When construction reached the first basement level, the design unit issued a change order: to create an equipment opening in the middle of the original 12-meter-long shear wall Q-3 on the first basement level, splitting it in the model into two walls, one 8.2 meters long and the other 3.1 meters long.

[0058] In the V3.2 version model before the upgrade, the permanent component identification of this shear wall was P00126-01-B01-CE-SWL-7C41B9A20D3E5F86, under which there was a steel reinforcement concealment acceptance record, eighteen on-site photos and a concrete material batch record.

[0059] After the design unit delivers the V3.3 version model, the model parsing unit 110 parses the model and extracts the geometric and attribute information of each component (step S101). The spatial matching unit 210 performs a search based on the outer bounding box of the shear wall before the upgrade (step S102): the distances between the center points of the outer bounding boxes of the two walls after the upgrade and the center points of the outer bounding boxes of the components before the upgrade are 2,980 mm and 3,050 mm respectively, both greater than the first threshold of 50 mm, so the one-to-one matching condition is not met; however, the overlap volume of the union of the outer bounding boxes of the two walls and the outer bounding box of the components before the upgrade accounts for 91% of the volume of the components before the upgrade, which is greater than the second ratio of 85%. After verification, the attribute matching unit 220 confirms that the component type of both is shear wall, the professional type is civil engineering, the floor is the first basement level, and the material grade is C35, which is consistent with the components before the upgrade (step S103). Based on this, the relationship determination unit 230 determines the inheritance mapping relationship as one-to-many (step S104).

[0060] Data inheritance unit 240 inherits the permanent identifier P00126-01-B01-CE-SWL-7C41B9A20D3E5F86 from the largest wall with a length of 8.2 meters and uses it as the main component. The wall with a length of 3.1 meters is assigned the lower-level identifier P00126-01-B01-CE-SWL-7C41B9A20D3E5F86-01 (step S105). Subsequently, the data is attached according to the collection location of the business data (step S106): of the eighteen on-site images, twelve images whose collection location falls within the horizontal projection range of the outer enclosure box of the 8.2-meter wall are attached to the main component, and six images whose collection location falls within the projection range of the 3.1-meter wall are attached to the lower-level components; the steel reinforcement concealment acceptance record is attached to the main component and marked as inherited from version V3.2 because the collection location is not recorded; the concrete material batch record is attached to both walls and the source identifier is retained. Change trace unit 250 records the current mapping relationship, mapping type (one-to-many), effective version number V3.3, and operation time (step S107).

[0061] After the above processing is completed, on-site personnel can still view the concealed steel reinforcement acceptance records and images that were generated before the change by scanning the QR code of the component in that area. The component file is not interrupted due to the design change. In contrast, if the existing technology is used, the two walls in the V3.3 version model are newly built components with brand new component identifiers. The nineteen business data originally attached to Q-3 will all lose their association and need to be manually searched and attached one by one.

[0062] Example 3 This embodiment uses the concrete pouring operation of the roof slab of the five-story, three-zone building of the above-mentioned project as an example to illustrate the process of on-site data collection and progress determination.

[0063] Before the pouring operation begins, the team leader uses a field terminal in the fifth-floor elevator lobby to scan the positioning QR code pasted on the side of the frame column. Based on this, the positioning unit 310 obtains that the column is located on the fifth floor above ground, with planar coordinates of (38.20, 15.60), and the gyroscope and magnetometer read its horizontal orientation angle as 112 degrees (the step corresponds to the processing of the field acquisition module 300). The candidate screening unit 320 constructs a screening area with the planar position as the vertex, a sector of ±45 degrees centered on 112 degrees, and a radius of 15 meters. After superimposing the filtering conditions of the fifth floor above ground and the professional field as civil engineering, it retrieves fourteen candidate components from the spatial index and returns them in order of distance. The cast-in-place slab B-5-12 to be poured is ranked second. After the team leader selects it, the association is completed without having to expand the model tree level by level.

[0064] The data acquisition unit 330 automatically loads the data acquisition form according to the current concrete pouring node of the component. The team leader uploads the pouring order, six images of the pouring process, the test block placement record, and the pouring team information. The status advancement unit 520 detects that in the preceding process nodes of the component, the formwork acceptance was completed the day before and the acceptance conclusion was qualified, the concealed reinforcement acceptance was also qualified, and the necessary business data for this node is complete and the acceptance conclusion is qualified. Therefore, it automatically sets the concrete pouring node to complete. Since there is still an incomplete physical strength testing node in the process node sequence of the component, the process status of the component is set to in progress, and the display driving unit 530 displays it in yellow in the model.

[0065] Seven days later, the tester uploaded the rebound test record for the slab, and the conclusion was satisfactory. The solid strength test node met the conditions for process completion, and the process status of the component was set to completed. The display drive unit 530 displayed it in green and included the 86.4 cubic meters of the slab in the progress of the fifth floor above ground. After comparing it with the four-dimensional progress plan, the system output a progress deviation prompt indicating that this section was one day behind schedule. Throughout the entire process, the management personnel did not perform any progress reporting operations.

[0066] In contrast, if a work group submits a concrete pouring record before the formwork acceptance is completed, the status advancement unit 520 will not advance the process status of that component and will output a process reversal alarm to the quality inspector and production manager, thereby preventing the situation of not having passed the advanced inspection from being included in the progress.

[0067] In addition, there is no mobile communication network coverage on the three underground floors of the project. The business data collected by the workers in this area is temporarily stored locally on the field terminal by the offline cache unit 340 and forms an upload queue. After the workers return to the ground, the data is automatically uploaded in order. Since the permanent component identifier is bound during the temporary storage, even if the model is upgraded once during this period, the data association module 400 can still accurately attach the batch of data to the upgraded component according to the permanent component identifier and mapping relationship table.

[0068] Example 4 This example illustrates the quality closure process and post-project delivery traceability. During construction, a quality inspector discovered honeycomb-like pitting on a shear wall on the second basement level. The inspector scanned a location QR code on the on-site terminal, selected the component, and generated a problem report with a permanent identifier for the component, a demolding and curing process node code, a responsible work team identifier, and a three-day rectification period. After the responsible work team completed the repairs and uploaded the rectification video from the same camera position, the problem report was closed upon the quality inspector's verification. The component's display in the model then changed from red to the color corresponding to its original process status.

[0069] Two years after the project was delivered, leaks appeared on the second basement level. Maintenance personnel used their mobile phones to scan the QR codes on the wall components. The traceability module 700 output a complete file for the component based on its permanent identifier: the component had been split in version V3.3 due to changes in equipment openings, and upgraded in version V4.1 due to adjustments in the protective layer thickness; the mapping relationship between the two upgrades and the business data inheritance records could be found. The file also included the batch number, manufacturer, certificate number, and retest report number of the waterproof membrane used in that area, the concrete pouring date, the pouring team and on-site personnel, as well as the acceptance images after demolding and the closed-loop rectification record of the aforementioned honeycomb and pitted surface issue. Based on this, the maintenance personnel traced back by batch number, quickly locating seven other walls on the second basement level that used the same batch of waterproof membrane, thus including them in the investigation.

[0070] As can be seen from the above embodiments, the present invention enables on-site business data to remain associated with components even after multiple model upgrades by using permanent component identifiers and inheritance mapping relationships; it greatly simplifies on-site data association operations by using candidate component screening based on location information; it makes the progress of the process objective and reliable by using business data to drive the progress of the process status; and on this basis, it achieves full-process traceability of engineering quality.

[0071] The above embodiments merely illustrate several implementation methods of the present invention, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these all fall within the protection scope of the present invention. Therefore, the protection scope of this invention patent should be determined by the appended claims.

Claims

1. A smart building engineering management system based on a BIM platform, characterized in that, include: The model processing module is used to parse the BIM model, obtain the geometric and attribute information of each component, and generate a unique permanent component identifier for each component based on the geometric and attribute information. The version mapping module is used to establish an inheritance mapping relationship based on the geometric and attribute information of components before and after the upgrade when the BIM model is upgraded, and to assign the permanent component identifier of the component before the upgrade to the upgraded component with the inheritance mapping relationship. The field acquisition module is used to acquire the location information of the field terminal and return the candidate components located within the range indicated by the location information to the field terminal. The data association module is used to store business data uploaded by field terminals, using the permanent identifier of the selected candidate component as an index. The progress engine module is used to update the process status of a component when its business data meets the preset process completion conditions, and drive the display of the BIM model according to the updated process status.

2. The intelligent building engineering management system based on a BIM platform according to claim 1, characterized in that, The model processing module includes an identifier generation unit; The identifier generation unit is used to extract the coordinates of the center point of the outer bounding box of the component in the project base point coordinate system, the floor to which the component belongs, the professional type and the component type, and then encodes the extracted results and splices them to generate a permanent identifier for the component. The permanent component identifiers and the component identifiers that come with the BIM model are stored separately and independently.

3. The intelligent building engineering management system based on a BIM platform according to claim 1, characterized in that, The version mapping module includes: The spatial matching unit is used to search for components in the upgraded components whose center point distance is less than a first threshold and whose overlap volume with the outer bounding box is greater than a first proportion, based on the outer bounding box of the component before the upgrade, to obtain a candidate mapping set. The attribute matching unit is used to perform attribute verification on the components in the candidate mapping set and remove components whose component type, professional type, floor or material grade is inconsistent with the components before the upgrade. The relationship determination unit is used to determine whether the inheritance mapping relationship is one-to-one, one-to-many, or many-to-one based on the number of components in the verified candidate mapping set and their correspondence with the components before the upgrade.

4. The intelligent building engineering management system based on a BIM platform according to claim 3, characterized in that, The version mapping module also includes a data inheritance unit, which is used for: When the inheritance mapping relationship is one-to-one, the business data of the component permanent identifier and its index of the component before the upgrade will be assigned to the component after the upgrade. When the inheritance mapping relationship is one-to-many, the permanent component identifier of the component before the upgrade is assigned to the component with the largest volume after the upgrade, and the lower-level identifiers derived from the permanent component identifier are assigned to the remaining components after the upgrade. The business data is then attached to the components after the upgrade according to the location of the business data collection. When the inheritance mapping relationship is many-to-one, the business data of each component index before the upgrade will be attached to the upgraded component, and the source identifier of the business data will be retained. Furthermore, if the relationship determination unit fails to determine the inheritance mapping relationship, the corresponding component is written into the confirmation queue, and the inheritance mapping relationship is written back after receiving the confirmation instruction.

5. The intelligent building engineering management system based on a BIM platform according to claim 4, characterized in that, The version mapping module also includes a change trace unit, which records the inheritance mapping relationship, mapping type, effective version number and operation time for each version upgrade, and restores the association relationship between components and business data according to the specified version number when a backtracking instruction is received.

6. The intelligent building engineering management system based on a BIM platform according to claim 1, characterized in that, The on-site data acquisition module includes: The positioning unit is used to receive the location code obtained by the field terminal scanning the positioning tag, or to receive the beacon signal collected by the field terminal, so as to obtain the floor and plane position of the field terminal. The candidate filtering unit is used to form a filtering area based on the planar position, according to a set radius and a set horizontal orientation angle range. It retrieves the components located within the filtering area from the spatial index stored in blocks according to floors and axis grids, and returns them in order of distance from the planar position from near to far. The data acquisition unit is used to receive business data uploaded by field terminals. The business data includes process node codes, image files, acceptance conclusions, and operator identification.

7. The intelligent building engineering management system based on a BIM platform according to claim 6, characterized in that, The field acquisition module also includes an offline caching unit, which is used to temporarily store business data and the permanent identifier of the selected candidate components locally on the field terminal when the field terminal is disconnected from the server, and upload them in the order of temporary storage after the connection is restored. The data association module is also used to retain the data with the larger model version number when multiple business data entries exist under the same permanent identifier of the same component.

8. The intelligent building engineering management system based on a BIM platform according to claim 1, characterized in that, The progress engine module includes: The state machine unit is used to configure the sequence of process nodes according to the component type and to configure the process completion conditions for each process node. The process completion conditions include that the necessary business data of the process node is complete and the acceptance conclusion is qualified. The status advancement unit is used to set the process node as completed when the process node of the component meets the process completion conditions, and to suspend advancement and output a process reversal alarm when the preceding process node of the process node is not completed. The display driving unit is used to assign different display states to the corresponding components in the BIM model according to the current process status of the components, and to count the amount of work completed by floor or flow section.

9. The intelligent building engineering management system based on a BIM platform according to claim 1, characterized in that, Also includes: The quality closed-loop module is used to generate problem forms that are bound with permanent component identifiers, process node codes and responsible person identifiers. After receiving a rectification response, it triggers a re-inspection and outputs an upgrade warning if the re-inspection fails to pass the rectification deadline. The traceability module is used to bind the batch information of incoming materials with the permanent identification of components, generate a component QR code corresponding to the permanent identification of the component, and output the version change record, process record, material batch information and image file of the corresponding component when the component QR code is scanned.

10. A smart building project management method based on a BIM platform, applied to a smart building project management system based on a BIM platform as described in any one of claims 1 to 9, characterized in that, include: Analyze the BIM model and generate a unique permanent identifier for each component based on its geometric and attribute information; When upgrading a BIM model, an inheritance mapping relationship is established based on the geometric and attribute information of the components before and after the upgrade, and the business data of the permanent component identifier and its index of the components before the upgrade are assigned to the upgraded components with the inheritance mapping relationship. Obtain the location information of the field terminal, return the candidate components within the range indicated by the location information to the field terminal, and store the business data uploaded by the field terminal using the permanent component identifier of the selected candidate component as an index; When the business data of a component meets the preset process completion conditions, the process status of the component is updated, and the display of the BIM model is driven according to the updated process status.

Images