BIM model metering and pricing method based on acceptance driving and electronic device

Abstract

This invention relates to the field of construction project information management technology, and provides an acceptance-driven BIM model measurement and pricing method and electronic device. The method includes: acquiring a three-dimensional building information model of the building project, controlling the component granularity to be no larger than the inspection batch granularity and establishing a mapping relationship; acquiring acceptance data for each inspection batch through a mobile terminal acceptance system, and linking the acceptance completion time to the corresponding model component according to the mapping relationship; filtering all model components according to the measurement cycle, automatically extracting the quantity of work for each model component and calculating the pricing amount; acquiring the declaration data submitted by the construction unit, comparing the BIM pricing amount with the declaration data in multiple dimensions and calculating the deviation rate, and outputting the audit result based on a threshold. This invention achieves objective quantification of progress and automatic extraction of quantities, improves the objectivity, accuracy, and efficiency of progress payment audits, and realizes full-process data traceability and auditability.

Description

Technical Field

[0001] This invention relates to the field of information management technology for construction projects, and in particular to a BIM model measurement and pricing method and electronic equipment based on acceptance-driven methods. Background Technology

[0002] In the construction process of engineering projects, progress payment measurement and pricing are crucial for payment. In the existing project management model, the construction unit typically submits progress payment measurement and pricing data to the supervision unit and the construction unit according to the construction schedule. Payment is then made after review and confirmation. The existing process mainly includes: the construction unit compiling a progress schedule; breaking down the work volume based on the progress schedule to form a measurement application form; forming a pricing application form based on the work volume and quota rules; submitting it to the cost estimator for review after review by the supervision unit; and finally, confirmation by the construction unit.

[0003] However, the existing scheme's progress review process suffers from a significant lack of objectivity. Progress is typically expressed as a percentage of completion, such as 30% completion of raft foundation pouring in this phase. Supervision units primarily rely on on-site inspections and subjective experience to judge the reasonableness of this percentage. This method lacks quantitative evidence, and different supervisors may disagree on the same progress. Furthermore, the scope of on-site inspections is limited, making it difficult to accurately assess the progress of concealed works or complex areas. This subjective judgment directly leads to difficulties in ensuring the credibility and consistency of progress review results.

[0004] More importantly, there is no direct mapping between the progress of the project and the actual quantities of work. In the current process, the progress is described only as a percentage of the construction status, failing to directly correlate with specific quantities of concrete, steel reinforcement, and formwork. This necessitates manual breakdown by cost estimators based on experience. This breakdown process is not only inefficient but also prone to errors due to differences in calculation rules and operational oversights, leading to discrepancies between measurement results and the actual on-site construction conditions. Because the supervision unit focuses on progress verification while the cost estimator focuses on verification of measurement and pricing rules, they employ different data foundations and working logics, resulting in a disconnect between progress information and quantity information, and a disconnect between measurement and pricing verification and actual on-site conditions.

[0005] Furthermore, current progress payment audits rely primarily on manual verification, lacking automated data comparison and anomaly warning mechanisms, making it difficult to quickly identify common issues such as over-reporting, under-reporting, or duplicate reporting. The quantity of work cannot be traced back to specific construction components or acceptance units, hindering refined cost control throughout the entire process. Although some existing technologies have proposed BIM (Building Information Modeling)-based construction progress management or automated pricing methods, these methods still rely on traditional manual reporting of visual progress or static model attributes. They fail to objectively quantify the actual on-site progress and link it to model data in real time, and also fail to address the issue of consistency in basic data between progress verification and quantity calculation. Summary of the Invention

[0006] Therefore, it is necessary to address the problems of insufficient objectivity in the progress review process of existing solutions, lack of direct mapping between progress and specific quantities of work, and lack of automated data comparison and anomaly warning mechanisms. To address these issues, a BIM model measurement and pricing method and electronic equipment based on acceptance-driven approach should be provided. By using the acceptance completion time to drive model data updates, the automatic extraction and pricing review of quantities of work can be achieved, thereby improving the objectivity and efficiency of the review.

[0007] This invention provides a BIM model measurement and pricing method based on acceptance-driven assessment, comprising: acquiring a three-dimensional building information model of a building project, wherein the granularity of each model component is controlled to be no larger than the granularity of the on-site inspection batch, each model component does not exist across inspection batches, and is pre-set with measurement and pricing attribute information including at least a list code and a quota code, and is assigned a globally unique identifier, and a mapping relationship is established with the inspection batch code of the inspection batch to which it belongs; acquiring acceptance data of each inspection batch through a mobile terminal acceptance system, wherein the acceptance data includes at least the acceptance status of the inspection batch and the acceptance completion time automatically recorded by the system when the supervisor completes the acceptance operation on the mobile terminal acceptance system; automatically linking the acceptance completion time to the corresponding model component according to the mapping relationship, as the actual completion time of the model component, wherein when an inspection batch corresponds to multiple model components, the acceptance completion time of the inspection batch is simultaneously linked to the multiple model components; and calculating according to a preset... The measurement cycle involves selecting all model components from the Building Information Model (BIM) whose actual completion time falls within the measurement cycle, forming a set of completed components for the current period. Based on this set, the quantities of each model component are automatically extracted, and the pricing amount for each component is automatically calculated according to the measurement and pricing attribute information. This results in a total pricing amount for the current period based on the BIM model. The application data submitted by the construction unit is obtained, and the pricing amount for the current period based on the BIM model is compared with the application data in multiple dimensions, including at least the total amount, the quantities of each component, and the unit price. The deviation rate is calculated for each dimension. The deviation rate is compared with a preset deviation threshold. If the deviation rate is less than or equal to the threshold, the process is considered successful. Otherwise, an alert is triggered, and a discrepancy analysis task is generated, requiring the submission of review materials. After review and confirmation, the process continues, ultimately outputting a review result containing the pricing amount for the current period based on the BIM model, the application amount, the deviation rate, and a detailed breakdown of discrepancies.

[0008] In one embodiment, controlling the granularity of each model component to be no larger than the granularity of the on-site inspection batch includes: splitting the model during the model creation stage according to the inspection batch boundaries defined by the unified standard for construction quality acceptance of building engineering, so that a single model component does not exist across inspection batches, and presetting a unique identifier in each model component that is consistent with the code of the inspection batch to which it belongs.

[0009] In one embodiment, establishing the mapping relationship includes: setting an inspection batch code field in the model component attribute field that uses the same coding rules as the acceptance system, forming a mapping database between the component's globally unique identifier and the inspection batch code.

[0010] In one embodiment, obtaining the acceptance data of each inspection batch through the mobile terminal acceptance system includes: receiving the acceptance data pushed by the acceptance system in JSON format through an open API interface, wherein the JSON data includes at least the inspection batch code, acceptance status, acceptance completion time, and location code.

[0011] In one embodiment, automatically attaching the acceptance completion time to the corresponding model component includes: parsing the inspection batch code in the JSON data, matching the corresponding globally unique identifier of the model component according to the mapping database, and writing the acceptance completion time into the actual completion time attribute field preset by the component; when there is a component without an attached timestamp, the system automatically marks it as a mapping anomaly and triggers manual verification.

[0012] In one embodiment, the step of selecting all model components whose actual completion time falls within the preset measurement period from the building information model includes: calling the time filtering function in the building information model platform to extract all components whose actual completion time attribute value falls within the range of the start time to the end time of the measurement period, forming a set of completed components for this period.

[0013] In one embodiment, the automatic extraction of the quantities of each model component includes: calling the API of the building information modeling platform to obtain the geometric parameters of the component, and automatically calculating the quantities of concrete, steel reinforcement or formwork in combination with the pre-set quantity calculation rules corresponding to the bill of quantities code; the calculation of the pricing amount includes automatically applying the corresponding unit price and fee rules according to the pre-set quota code for summarization.

[0014] In one embodiment, the multi-dimensional comparison includes: comparing the total amount, the quantity of each sub-item of work, and the unit price of each item in the bill of quantities item by item, and calculating the deviation rate for each dimension; the deviation rate is calculated according to the following formula: in, The corresponding value in the declared data. The value is calculated based on Building Information Modeling.

[0015] In one embodiment, the preset deviation threshold includes a multi-level threshold system: setting a first-level threshold, a second-level threshold, and a third-level threshold, wherein the first-level threshold is less than the second-level threshold, and the second-level threshold is less than the third-level threshold; when the deviation rate is within the range of the first-level threshold, it automatically passes; when the deviation rate exceeds the first-level threshold but is within the range of the second-level threshold, a yellow warning is triggered and a difference description requirement is generated; when the deviation rate exceeds the second-level threshold but is within the range of the third-level threshold, a red warning is triggered and the payment process is suspended, and on-site verification is mandatory.

[0016] In one embodiment, the output of the audit results includes generating a progress payment audit report, which includes the current period pricing amount based on the building information model, the amount declared by the construction unit, the deviation rate of each dimension, the difference details, and the suggested payment amount, and realizes full-process data traceability.

[0017] In one embodiment, triggering the early warning and generating the discrepancy analysis task further includes: when the yellow or red warning is triggered, extracting all associated model components to form a deviation component set based on the list of items causing the deviation; retrieving the audit result data of each component in the deviation component set within the approved historical measurement period, the audit result data including the BIM calculated engineering quantity of each component within the historical period; calling the API of the building information modeling platform to obtain the geometric parameters of each deviation component, calculating the total BIM engineering quantity of each component; and comparing the BIM calculated engineering quantity of each component within the historical period with the current period. The BIM calculation of the cumulative quantity of the component is performed. When the cumulative value exceeds the total BIM quantity of the component, the component is marked as a duplicate component. The unit price of each item in the bill of quantities associated with the deviation component set is extracted in the most recent three measurement periods. When the unit price of a certain item changes in the same direction for two consecutive measurement periods and the change exceeds a preset proportion, the item is marked as a unit price trend abnormal item. In the difference analysis task, the construction unit is required to provide a recalculation draft of the quantity of the duplicate component for each item and a detailed analysis table of the unit price composition for each item in the unit price trend abnormal list. Failure to provide these will result in the application not being approved.

[0018] In one embodiment, for the duplicated application components, the following further processing is performed: Spatial proximity clustering and optimal review path generation: Based on the three-dimensional spatial coordinates of each component in the building information model, duplicated application components located on the same floor and belonging to the same professional zone are grouped into the same on-site review cluster; for each on-site review cluster, the shortest path algorithm is used to calculate the optimal movement route for on-site review personnel, generating an optimal review path map including the review order; Cluster-level quantity balance verification: For each on-site review cluster, the API of the building information model platform is called to obtain the quantities of all components within the cluster. Geometric parameters are used to calculate the sum of the total BIM quantities of all components within the cluster. The historical BIM quantities of all components within the cluster are added to the current BIM quantities. When the added value exceeds the sum of the total BIM quantities, the cluster is marked as a quantity overdraft cluster. Mandatory on-site verification is then implemented: the quantity overdraft cluster is pushed to the mobile acceptance system, requiring supervisors to conduct on-site verification of all components within the cluster according to the optimal verification path and enter verification conclusions item by item. If any component has not entered a verification conclusion, the corresponding list item will not be included in the current approval process.

[0019] The present invention also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the acceptance-driven BIM model measurement and pricing method as described above.

[0020] The aforementioned acceptance-driven BIM model measurement and pricing method and electronic equipment, by controlling the granularity of model components to be no larger than the granularity of inspection batches and not existing across inspection batches, and by pre-setting measurement and pricing attribute information in model components and establishing a mapping relationship between unique component identifiers and inspection batch codes, provides an objective and granular basis for subsequent data association. The mobile acceptance system automatically obtains the acceptance completion time, replacing the traditional manual reporting of progress, so that progress determination no longer relies on the subjective judgment of the supervisor, but is automatically recorded and generated by the system upon acceptance completion, thus achieving objective quantification of progress. By automatically linking the acceptance completion time to the corresponding model component according to the mapping relationship as the actual completion time, each model component has a unique and objective completion timestamp. This establishes a direct mapping relationship between progress and quantity of work, eliminating the need for manual breakdown in traditional methods and the resulting errors and inconsistencies. Furthermore, it filters component sets with actual completion times according to the measurement cycle, automatically extracts quantities from the model, and calculates pricing amounts based on pre-set measurement and pricing attributes, achieving automatic correlation between measurement and pricing and actual on-site progress. Finally, through multi-dimensional comparison with data submitted by construction units and deviation rate threshold judgment, it automates and makes the review process traceable, effectively overcoming the problems of subjective progress judgment, inconsistent data foundations due to the disconnect between progress and quantity of work, and low efficiency of manual review in existing solutions. This gives the progress payment measurement and pricing process an overall technical effect of objectivity, quantification, and traceability. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0022] Figure 1 This is a flowchart of the acceptance-driven BIM model measurement and pricing method according to an embodiment of the present invention. Figure 2 This is a mapping diagram of BIM model measurement and pricing data based on acceptance-driven method according to an embodiment of the present invention; Figure 3 This is a framework diagram for deep difference analysis and anomaly identification in an embodiment of the present invention; Figure 4 This is an internal structural diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0024] The following is combined with Figures 1-4 This invention describes the acceptance-driven BIM model measurement and pricing method and electronic equipment.

[0025] like Figure 1 As shown in one embodiment, an acceptance-driven BIM model measurement and pricing method uses the acceptance completion time as the core driving factor to replace the traditional manual reporting of progress. It constructs a closed-loop logic from obtaining on-site acceptance data to automatically outputting the pricing amount, achieving objective quantification and automation of progress payment review. Compared with existing technologies, the method in this embodiment has significant innovation. In existing technologies, the progress review process suffers from significant objectivity issues. Supervision units mainly rely on on-site inspections and subjective experience to judge the progress ratio. This judgment method lacks quantitative basis, and different supervisors may have differing opinions on the same progress. More importantly, there is no direct mapping relationship between progress and specific quantities. Progress only describes the construction status in proportion and cannot directly correspond to specific quantities such as concrete, steel reinforcement, and formwork. Cost estimators must manually break it down based on experience, leading to inconsistencies between measurement results and actual on-site construction conditions. Furthermore, existing progress payment reviews mainly rely on manual verification, lacking automated data comparison and anomaly warning mechanisms, making it difficult to quickly identify common problems such as over-reporting, under-reporting, or duplicate reporting. This embodiment achieves objective quantification of progress recognition by driving model data updates through acceptance completion time, establishes a direct mapping relationship between visual progress and engineering quantity, and realizes automated review through multi-dimensional comparison and multi-level threshold early warning mechanism, effectively solving the above problems.

[0026] Specifically, the method in this embodiment includes the following steps: Step S110: Obtain the three-dimensional building information model of the building project.

[0027] In this building information model, the granularity of each model component is controlled to be no larger than the granularity of the on-site inspection batch. Each model component does not exist across inspection batches and is pre-set with measurement and pricing attribute information including at least the list code and quota code. It is also assigned a globally unique identifier and has a mapping relationship with the inspection batch code of its respective inspection batch.

[0028] During the model creation phase, modelers need to split or create BIM model components according to the inspection batch division scheme determined by the "Unified Standard for Acceptance of Construction Quality of Building Engineering". For example, if the acceptance of a section of concrete wall on a certain floor is divided into an independent inspection batch, then in the BIM model, this section of wall should exist as an independent model component, and cannot be merged with the walls of adjacent inspection batches, thus ensuring a one-to-one correspondence between model components and inspection batches in space and attributes. Each model component is assigned a globally unique identifier, such as a GUID, and a bill of quantities code (such as 010503005001) and a quota code are pre-set in the attribute fields so that cost information can be directly extracted later. By establishing a mapping database between inspection batch codes and component GUIDs, a data foundation is laid for the automatic linking of acceptance data.

[0029] Step S120: Obtain acceptance data for each inspection batch through the mobile acceptance system. This acceptance data includes at least the acceptance status of the inspection batch and the acceptance completion time automatically recorded by the system when the supervisor completes the acceptance operation on the mobile acceptance system.

[0030] Unlike the traditional method where construction units fill out progress reports, this step uses a mobile acceptance system as the data source. When inspecting batches on-site, supervisors input acceptance information via mobile devices (such as smartphones or tablets). The system automatically records the server's standard time as the acceptance completion time the moment the supervisor clicks the "Accept Acceptance" button, and generates an acceptance data package containing the batch code, acceptance status (qualified / unqualified), completion time, and location code. This timestamp is automatically generated by the system, ensuring objectivity and immutability, effectively preventing errors caused by human error in reporting progress or false declarations.

[0031] Step S130: Based on the mapping relationship, the acceptance completion time is automatically linked to the corresponding model component as the actual completion time of that model component. Where a certain inspection batch corresponds to multiple model components, the acceptance completion time of that inspection batch is simultaneously linked to all of the multiple model components.

[0032] After receiving the acceptance data pushed from the mobile device, the system backend parses the inspection batch code and retrieves the matching model component GUID from the mapping database. Once a match is found, the system writes the acceptance completion time into the actual completion time attribute field of the corresponding model component. For example, an inspection batch "JYP-01-03-001" contains three model components. When the inspection batch passes acceptance, the system synchronously writes the same acceptance completion time into the attributes of all three components. This process achieves real-time synchronization between the acceptance progress in the physical world and the model status in the digital world.

[0033] Step S140: According to the preset measurement period, select all model components whose actual completion time falls within the measurement period from the building information model to form the set of completed components for this period.

[0034] The measurement period is typically set monthly or by milestones, for example, from March 1, 2024 to March 31, 2024. The system calls the time filtering function of the BIM platform, traverses all components in the model, and extracts components whose actual completion time attribute values ​​fall within this time interval. These components constitute the set of physical entities that have been completed and accepted in this phase, providing an accurate data range for subsequent quantity calculations and avoiding duplicate or missed calculations of quantities due to ambiguous progress definitions in traditional methods.

[0035] Step S150: Based on the completed component set for this period, automatically extract the engineering quantity of each model component, and automatically calculate the pricing amount of each corresponding component according to the measurement and pricing attribute information, and summarize to obtain the pricing amount for this period based on the BIM model.

[0036] The system uses the BIM platform's API interface to batch read the geometric parameters (such as volume, area, and length) of each component in the current phase's completed component set. Based on pre-set quantity calculation rules corresponding to the bill of quantities codes (such as deducting the thickness of the steel reinforcement protective layer), it automatically calculates quantities such as concrete volume, steel reinforcement weight, or formwork area. Subsequently, the system automatically applies the corresponding quota items and fee standards according to pre-set quota codes to calculate the total price of each component and summarizes the results to generate the current phase's pricing amount based on the BIM model. This process achieves automatic conversion from geometric model data to cost data, eliminating errors from manual quantity calculation.

[0037] Step S160: Obtain the application data submitted by the construction unit, compare the current period pricing amount based on the BIM model with the application data in multiple dimensions including at least the total amount, the quantity of each item of work and the unit price, and calculate the deviation rate under each dimension.

[0038] The data submitted by construction companies typically includes the declared quantities, unit prices, and total amounts. The system automatically calculates the quantities, unit prices, and total amounts using BIM and compares them item by item with the declared data. For example, it compares the quantities of concrete and the unit prices of steel reinforcement, and calculates the deviation rate to quantify the degree of difference between the declared data and the model-calculated data.

[0039] Step S170: Compare the deviation rate with the preset deviation threshold. If the deviation rate is less than or equal to the deviation threshold, the process is considered successful. Otherwise, trigger an alert and generate a difference analysis task, requiring the submission of review materials. After review and confirmation, the process continues, and the final output includes the current pricing amount, declared amount, deviation rate, and difference details based on the BIM model.

[0040] The system incorporates a deviation threshold logic. For projects with deviation rates within the allowable range, the system automatically approves the audit, improving efficiency. For projects with deviation rates exceeding the threshold, the system automatically triggers an early warning mechanism, generates a discrepancy analysis task, and notifies the construction unit to submit relevant supporting documents for manual review. The final audit report not only includes monetary data but also details the deviations, achieving full data traceability and audit process, providing comprehensive evidence for subsequent project audits.

[0041] In one embodiment, the preprocessing procedure for the building information model and the mechanism for establishing mapping relationships are further described in detail.

[0042] During the model creation phase, it is necessary to control the granularity of each model component to be no larger than the granularity of the on-site inspection batch. Specifically, this includes splitting the model according to the inspection batch boundaries defined by the unified standard for construction quality acceptance of building engineering, ensuring that a single model component does not exist across inspection batches, and pre-setting a unique identifier in each model component that is consistent with the code of its respective inspection batch.

[0043] Specifically, traditional modeling often focuses on building function or overall structure, such as merging multiple wall sections on the same floor into a single model component. This can result in the geometric extent of the model component potentially spanning multiple inspection batches. In this embodiment, however, modelers must physically decompose components in the BIM modeling software according to the construction quality acceptance plan. For example, if a section of concrete wall on a certain floor is divided into two inspection batches (such as inspection batch A and inspection batch B) in the construction plan, then in the BIM model, this section of wall must be decomposed into two independent model components (such as wall component A and wall component B), ensuring that the spatial extent of each model component strictly falls within the boundary of a single inspection batch. This granular consistency control mechanism forms the basis for subsequent data integration, guaranteeing the atomicity of data mapping. That is, one acceptance data point corresponds to only one or a set of specific model components, avoiding the ambiguity in acceptance data attribution caused by components spanning multiple inspection batches, thereby ensuring the accuracy of quantity calculations.

[0044] Furthermore, in order to achieve accurate association between acceptance data and model components, a mapping relationship needs to be established. Specifically, this includes setting an inspection batch code field in the attribute fields of the model components that uses the same coding rules as the acceptance system, forming a mapping database between the globally unique identifier of the component and the inspection batch code.

[0045] During BIM model creation, the system automatically assigns a globally unique identifier, such as a GUID, to each model component. Simultaneously, modelers enter the inspection batch code to which the component belongs in its attributes. This coding rule is completely consistent with the coding rule used by the mobile acceptance system. For example, the GUID of model component "Wall Component A" is "12345678-ABCD...", and the inspection batch code entered in its attribute field is "JYP-01-03-001". The system builds and maintains a mapping database on the backend server, which stores the correspondence between all component GUIDs and inspection batch codes. When the mobile acceptance system sends acceptance data containing the inspection batch code "JYP-01-03-001", the system can quickly locate the model component with the GUID "12345678-ABCD..." by querying the mapping database, thus achieving accurate data entry. This mapping mechanism effectively solves the data silo problem between the BIM platform and the acceptance system, ensuring that the acceptance progress in the physical world can be mapped to the model components in the digital world in real time and accurately.

[0046] In one embodiment, the data communication mechanism between the mobile acceptance system and the BIM platform, as well as the exception handling logic during the data writing process, are described in detail.

[0047] During the process of obtaining acceptance data for each inspection batch through the mobile terminal acceptance system, the system receives the acceptance data pushed by the acceptance system in JSON format through the open API interface. The JSON data includes at least the inspection batch code, acceptance status, acceptance completion time, and location code.

[0048] Specifically, the mobile acceptance system, acting as the data acquisition front-end, establishes a RESTful architecture-based communication connection with the BIM platform server. After the supervisor completes the inspection batch acceptance operation on-site, the mobile application automatically encapsulates an acceptance data packet. This data packet is serialized using JSON (JavaScript Object Notation) format. This lightweight data exchange format effectively reduces network transmission overhead and adapts to the unstable network environment of the construction site. The JSON data structure contains at least four key fields: "InspectionBatchCode" (inspection batch code) uniquely identifies the acceptance object; "Status" (acceptance status) indicates whether it is qualified or unqualified; "CompletionTime" (acceptance completion time) records a timestamp accurate to the second; and "LocationCode" (location code) is used to locate the floor or area. For example, a typical JSON data fragment might look like this: {"InspectionBatchCode":"JYP-02-05-003", "Status":"Qualified", "CompletionTime":"2024-03-15 14:30:00", "LocationCode":"FL-02"}. The BIM platform server is configured with a listening service. Once the JSON data stream is received, the subsequent parsing and processing process is triggered.

[0049] Furthermore, the process of automatically linking the acceptance completion time to the corresponding model component includes parsing the inspection batch code in the JSON data, matching the corresponding globally unique identifier of the model component according to the mapping database, and writing the acceptance completion time into the actual completion time attribute field preset by the component.

[0050] The system's backend service program first calls a JSON parser to extract the value of the "InspectionBatchCode" field, and then performs a query operation in a pre-built mapping database. Since the mapping database stores key-value pairs between inspection batch codes and model component GUIDs, the system can quickly locate the target model component. For example, if the parsed inspection batch code is "JYP-02-05-003", the system retrieves the corresponding GUID "Wall-South-02" from the database, and then calls the BIM platform's data writing interface to write the value of the "CompletionTime" field, "2024-03-15 14:30:00", into the "Actual Completion Time" attribute parameter of the wall component. This automated data flow mechanism eliminates the tedious process of manual data entry, ensuring the real-time nature and accuracy of model status updates.

[0051] Considering the potential risk of data inconsistency in real-world engineering environments, this embodiment also incorporates a robust anomaly handling mechanism. When a component lacks a timestamp, the system automatically marks it as a mapping anomaly and triggers manual verification.

[0052] Mapping anomalies are typically triggered in the following scenarios: First, the inspection batch code entered on the mobile device does not exist in the BIM model's mapping database, possibly due to inconsistent coding rules or missing model components. Second, JSON data packets may experience packet loss or missing fields during transmission, leading to parsing failure. Third, the target model component may be accidentally deleted or locked, causing the write operation to fail. When the system detects any of these situations, it will not directly interrupt the process. Instead, it will record the acceptance data as pending and generate a mapping anomaly log in the system management interface, while simultaneously sending a warning notification to project managers. Managers can manually intervene to verify the correspondence between the inspection batch code and the model component, correct the mapping database, or supplement the missing data before re-triggering the attachment process. This anomaly capture and manual fallback mechanism effectively prevents system crashes caused by localized data errors, ensuring the overall stability of the measurement and pricing process.

[0053] In one embodiment, the specific logic of time-based filtering and the technical implementation details of automatic quantity calculation are described in detail. Specific technical means are used to ensure the accuracy of the filtering results and the automated generation of pricing data.

[0054] According to the preset measurement cycle, all model components whose actual completion time falls within the measurement cycle are selected from the building information model to form the set of completed components for this period. Specifically, this includes: calling the time filtering function in the building information model platform to extract all components whose actual completion time attribute value falls within the range of the start time to the end time of the measurement cycle, and forming the set of completed components for this period.

[0055] The measurement period is typically preset by project managers in the system, for example, from 00:00 on March 1, 2024 to 24:00 on March 31, 2024. The system backend constructs a time filter by calling the secondary development interface (API) provided by the BIM platform. This filter iterates through all component instances in the model database, reading the value of their "actual completion time" attribute field one by one. The system compares the read timestamp with the start and end timestamps of the measurement period. If the actual completion time of a component is greater than or equal to the start time and less than or equal to the end time, the component is determined to be a completed component for this period and added to the set of completed components for this period. For example, the actual completion time of a concrete wall component is "2024-03-15 14:30:00," which falls within the aforementioned March period; therefore, this component is automatically filtered into the set. This process is entirely automated by the system backend, requiring no manual intervention, greatly improving the efficiency of defining the scope of progress payment measurement and avoiding omissions or duplicate statistics that may occur during manual screening.

[0056] Furthermore, based on the completed component set in this period, the engineering quantity of each model component is automatically extracted, including: calling the API of the building information modeling platform to obtain the geometric parameters of the component, and combining the engineering quantity calculation rules corresponding to the pre-set bill of quantities code to automatically calculate the engineering quantity of concrete, steel reinforcement or formwork; the calculation of the pricing amount includes automatically applying the corresponding unit price and fee rules according to the pre-set quota code for summarization.

[0057] In the quantity extraction phase, this embodiment employs specific API call logic to implement technology implementation. Taking the widely used Revit platform as an example, the system creates an element collector using the FilteredElementCollector class provided by the Revit API, traversing the components in the current completed component set. For concrete components, the system calls the geometric property interface of the component instance to directly read its volume parameters. It is worth noting that after reading the volume, the system corrects it according to the quantity calculation rules associated with the pre-set bill of quantities code (e.g., 010503005001). For example, according to the "Construction Engineering Quantity List Pricing Specification" (GB 50500), the concrete volume may need to deduct the volume occupied by the reinforcing steel or be adjusted according to the component type. The system's built-in calculation engine automatically executes these rule corrections to obtain quantity data that conforms to national standards. For reinforced concrete components, the system reads the diameter, length, and quantity parameters of the reinforcing steel and automatically calculates the weight based on physical formulas. For formwork quantities, the system extracts the surface area parameters of the component and performs deduction calculations according to contact surface rules.

[0058] During the pricing calculation phase, the system automatically retrieves the corresponding quota item from the cost database based on the pre-set quota code in the component attributes (e.g., quota number A4-1 for a certain region). The system reads the unit prices of labor costs, material costs, and machinery costs under that item, and performs multiplication calculations based on the calculated quantities. Simultaneously, the system automatically applies fee rules, such as the calculation of management fees, profits, and taxes, ultimately summarizing to generate the total price for the component. Through the API calls and the rule engine, the system achieves a fully automated conversion from 3D geometric model data to cost data, completely eliminating the inefficient traditional methods of manual drawing interpretation, quantity calculation, and quota lookup, significantly improving the accuracy and efficiency of measurement and pricing.

[0059] In one embodiment, the specific calculation logic for multi-dimensional comparison and the early warning mechanism based on a multi-level threshold system are described in detail. This is the core element for achieving automated progress payment review and risk-based hierarchical management.

[0060] Multi-dimensional comparison involves comparing the total amount, the quantity of each sub-item, and the unit price of each item in the bill of quantities, and calculating the deviation rate for each dimension. After obtaining the current period's pricing amount based on the BIM model and the data submitted by the construction unit, the system activates the multi-dimensional comparison engine. This engine not only compares the final total amount but also delves into the specific quantities of each sub-item (such as concrete volume and steel reinforcement weight) and the unit price of each item in the bill of quantities. This multi-dimensional comparison mechanism prevents "padding" behavior based on a single dimension; for example, construction units might adjust unit prices to compensate for inflated quantities. Multi-dimensional comparison effectively reveals such hidden cost deviations.

[0061] The deviation rate is calculated using the following formula: in, The corresponding value in the declared data. The value is calculated based on Building Information Modeling.

[0062] This formula uses the objective values ​​calculated by the BIM model as the benchmark (denominator) to calculate the deviation of the declared value from the benchmark value. For example, in a concrete sub-item, the BIM model automatically calculates the quantity of work based on the components to be inspected. 100m 3 The amount of work declared by the construction unit 105m 3 The deviation rate δ is calculated as |105-100| / 100×100%=5%. This standardized formula transforms the fuzzy differences into precise quantitative indicators, providing a data foundation for subsequent automated judgment.

[0063] Furthermore, to automate the review process, this embodiment pre-sets a multi-level threshold system for deviation thresholds: setting a first-level threshold, a second-level threshold, and a third-level threshold, where the first-level threshold is lower than the second-level threshold, and the second-level threshold is lower than the third-level threshold. This multi-level threshold system is designed to balance review efficiency and fund security, employing differentiated handling strategies for different levels of deviation risk to avoid wasting review resources or overlooking risks due to a "one-size-fits-all" approach. The specific judgment logic is as follows: The system automatically approves projects when the deviation rate falls within the first-level threshold. For example, if the first-level threshold is set to 3%, and the calculated deviation rate for a certain sub-item is 2%, falling within 3%, the system determines that the submitted data for that sub-item is basically consistent with the model's calculated data, falling within the normal range of construction losses or calculation errors. In this case, the system automatically marks the sub-item as approved, requiring no manual intervention, and directly proceeds to the amount summary stage. This significantly reduces the workload of auditors in handling routine compliance items and substantially improves audit efficiency.

[0064] A yellow alert is triggered and a discrepancy explanation requirement is generated when the deviation rate exceeds the first-level threshold but falls within the second-level threshold. For example, if the second-level threshold is set to 5%, and the deviation rate of a decoration project is 4.5%, exceeding 3% but not exceeding 5%, the system triggers a yellow alert. At this time, the system automatically generates a discrepancy explanation task and pushes it to the construction unit, requiring them to submit a reasonable explanation or supporting materials (such as design change orders or site visa forms) for the deviation within a specified time. Reviewers must verify the submitted discrepancy explanation and only release it after confirming its accuracy. This level of design not only intercepts risks for projects with certain deviations but also gives construction units the opportunity to prove their compliance with materials, ensuring the fairness of the process.

[0065] A red alert is triggered when the deviation rate exceeds the secondary threshold but falls within the tertiary threshold, suspending the payment process and mandating on-site verification. For example, the tertiary threshold is set at 10%. If the deviation rate for a certain steel reinforcement item reaches 8%, exceeding the secondary threshold of 5%, the system immediately triggers the highest-level red alert. At this time, the system automatically freezes the payment process for that item and adds it to the mandatory on-site verification list. Auditors must bring mobile devices to the construction site to conduct on-site measurement and verification of the actual completed steel reinforcement work. Only when the on-site verification data matches the declared data or BIM model data can the alert be lifted and the payment process resume. This mechanism effectively prevents the risk of false reporting of major project quantities and ensures the safety of fund payments.

[0066] It should be understood that the above threshold settings of 3%, 5%, and 10% are merely illustrative examples. In practical applications, project managers can dynamically adjust the thresholds at each level through the system configuration interface according to the project type, contractual agreement, and risk preference to adapt to the management needs of different projects.

[0067] In one embodiment, the output format of the audit results and the mechanism for full-process data recording and traceability are described in detail. This is a key link in achieving a closed loop of digital auditing and cost control.

[0068] The audit results output includes generating a progress payment audit report, which includes the current period's pricing amount based on the building information model, the amount declared by the construction unit, the deviation rate of each dimension, the details of the differences, and the recommended payment amount, and achieves full-process data traceability and auditability.

[0069] Once the system completes multi-dimensional comparisons and deviation rate calculations, it automatically generates a structured progress payment review report. This report not only includes traditional summaries of amounts, but more importantly, it contains detailed discrepancies. The discrepancy details table lists the BIM-calculated quantities, declared quantities, unit price differences, and total price differences for each item in the bill of quantities, and marks the corresponding deviation level (e.g., normal, yellow warning, red warning). The recommended payment amount is automatically calculated by the system based on the review logic. For projects with deviation rates within the threshold range, payment is made according to the BIM-calculated amount; for projects triggering warnings, payment is made according to the provisional amount after deducting the disputed amount, or adjusted after review.

[0070] Furthermore, this embodiment achieves component-level cost traceability by linking acceptance time, thereby ensuring full-process data traceability. Since the actual completion time attribute of each model component has been linked to the specific inspection batch acceptance completion time in the previous embodiment, and each component has a globally unique identifier, the system will establish a payment record-component set association index in the background database when generating the audit report.

[0071] When cost traceability is required, such as when auditors need to query the specific composition of a progress payment, the system can use this index to reverse-search for a list of all model components approved in the current period. Clicking on any component allows the system to retrieve its attribute information, displaying its acceptance completion time, corresponding inspection batch code, geometric dimensions, engineering quantity calculation formula, and applied quota item. This mechanism ensures that every payment amount can be accurately broken down to specific floors and specific components, achieving a strict correspondence between cash flow and physical quantity. It completely solves the pain points of vague and difficult-to-trace progress payment basis in the traditional model, providing detailed and tamper-proof data support for subsequent project settlement audits.

[0072] In one embodiment, refer to Figure 3 The document details the in-depth difference analysis mechanism after triggering an early warning and the intelligent auxiliary process for on-site verification. This is the high-level defense system built in this case to address common malicious false reporting and duplicate declaration behaviors in engineering cost audits.

[0073] When the system triggers a yellow or red alert, this embodiment goes beyond simple deviation notifications and proceeds with in-depth data mining and logical verification. Specifically, the system first extracts all associated model components from the list of items causing the deviation, forming a deviation component set. This set serves as the data foundation for all subsequent in-depth analyses, and the system will perform multi-dimensional anomaly identification on the components within this set.

[0074] First, the system retrieves the audit result data for each component in the deviation component set within the approved historical measurement periods. This audit result data includes the BIM calculated quantities of each component within the historical periods. Since components in the BIM model have globally unique identifiers, the system can trace the payment records of that component across all past measurement periods. Next, the system calls the Building Information Modeling (BIM) platform's API to obtain the geometric parameters of each deviation component and calculates the total BIM quantity for each component. Here, the total BIM quantity refers to the final designed quantity of the component in the model. The system adds the BIM calculated quantities of each component within the historical periods to the current period's BIM calculated quantities. When the added value exceeds the component's total BIM quantity, the component is marked as a duplicate application.

[0075] Specifically, for example, if the total design volume of a concrete column component is 10 cubic meters, and 8 cubic meters have been declared and paid for in previous measurement periods, and another 3 cubic meters have been declared in this period, the cumulative value is 11 cubic meters, exceeding the total BIM project volume of 10 cubic meters. The system determines that this component is suspected of being a duplicate declaration. This mechanism, through the logic of comparing historical accumulation with the total volume, effectively identifies hidden violations of duplicate declarations across periods, preventing overspending of project volume.

[0076] Secondly, the system also identifies anomalies from the unit price perspective. The system extracts the declared unit prices of each item in the bill of quantities associated with the deviation component set within the most recent three measurement periods. When the declared unit price of an item shows a consistent change in the same direction for two consecutive measurement periods, and the change exceeds a preset percentage, the item is marked as a unit price trend anomaly item. For example, if the declared unit prices of an item in the most recent three periods are 100 yuan, 105 yuan, and 110 yuan respectively, with two consecutive increases exceeding the preset 2% increase, the system determines that there is a risk of abnormal unit price fluctuations. In the difference analysis task, the system mandates that construction units provide recalculated quantities for each duplicated component and a detailed analysis table of unit price composition for each unit price trend anomaly item. Failure to provide these documents will result in disqualification. This mandatory evidentiary requirement increases the cost of irregular declarations and enhances the rigor of the review process.

[0077] For identified duplicate application components, this embodiment further refines the process by introducing spatial computation algorithms to assist on-site verification. First, spatial proximity clustering and optimal verification path generation are performed: based on the three-dimensional spatial coordinates of each component in the building information model, duplicate application components located on the same floor and belonging to the same professional zone are grouped into the same on-site verification cluster. Traditional verification is often fragmented, requiring supervisors to frequently move between different floors and areas, resulting in low efficiency. This embodiment uses a clustering algorithm to aggregate spatially adjacent and professionally related components into a cluster; for example, all suspicious column and beam components in the second-floor structural zone are grouped into a verification cluster. For each on-site verification cluster, the system uses a shortest path algorithm to calculate the optimal movement route for on-site verification personnel, generating an optimal verification path map that includes the verification order. This path map incorporates internal building access paths, planning the shortest inspection route for supervisors without backtracking, significantly improving the efficiency of on-site verification.

[0078] While generating the path, the system also performs cluster-level quantity balance verification. For each on-site verification cluster, the system calls the API of the Building Information Modeling (BIM) platform to obtain the geometric parameters of all components within the cluster and calculates the sum of the total BIM quantities of all components within the cluster. Subsequently, the historical BIM calculated quantities of all components within the cluster are added to the current BIM calculated quantities. When the accumulated value exceeds the sum of the total BIM quantities, the verification cluster is marked as a quantity overdraft cluster. This step performs total quantity control at the macro level of the "cluster" to prevent errors in individual components from masking overall over-reporting.

[0079] Finally, the system executes a mandatory on-site verification process. The overdraft cluster is pushed to the mobile acceptance system, mandating that supervisors verify each component within the cluster on-site according to the optimal verification path and enter the verification conclusions for each item. The system has a strict process blocking mechanism; if any component has not entered a verification conclusion, the corresponding item in the list will not be allowed to enter the current approval process. This design ensures the thoroughness of the on-site verification, prevents negligence or omissions by supervisors, and achieves intelligent supervision throughout the entire process, from anomaly identification and path planning to on-site closure.

[0080] In a specific embodiment, to verify the practical application effect of the acceptance-driven BIM model measurement and pricing method provided by the present invention, this embodiment is described in detail with reference to a specific engineering project. The project is a high-rise commercial office building with a total construction area of ​​approximately 50,000 square meters and a frame-core tube structure as its main structure. The project uses the method described in this invention to audit progress payments for a certain month (the measurement period is set from March 1, 2024 to March 31, 2024).

[0081] In this project, the project team first created a BIM model based on the construction quality acceptance plan, strictly controlling the granularity of model components to ensure that each component did not cross inspection batches, and pre-setting bill of quantities and quota codes. During construction, the supervisors used a mobile acceptance system for on-site acceptance. Taking March as an example, the supervisors completed the acceptance of approximately 150 inspection batches. Whenever the supervisors clicked "acceptance approved" on the mobile device, the system automatically recorded the precise acceptance completion time and pushed JSON data containing the inspection batch code, acceptance status, and acceptance completion time to the BIM platform server via API. The BIM platform's backend service program parsed this data in real time and, based on the pre-established mapping database, automatically linked the acceptance completion time to the corresponding model component attributes.

[0082] After the measurement period ends, the system automatically executes the measurement and pricing process. The system uses the time filtering function to extract all model components whose actual completion time falls between March 1st and March 31st, 2024, forming a set of completed components for this period. Subsequently, the system uses the Revit API to batch read the component geometric parameters, automatically calculates the quantities of concrete, steel reinforcement, etc., and combines this with pre-set quota information to generate the pricing amount for this period based on the BIM model. Simultaneously, the construction unit submits traditional application materials. The system compares the automatically calculated BIM data with the application data from multiple dimensions and applies a three-level threshold system for judgment. The results show that most sub-items have a deviation rate within 3% and automatically pass the review; a small number of decoration projects have a deviation rate of around 5%, triggering a yellow warning, which is approved after the construction unit submits a difference explanation online; a few steel reinforcement sub-items trigger a red warning due to a deviation rate exceeding 10%, and the system automatically generates a difference analysis task, marks suspected duplicate application components, and mandates on-site verification.

[0083] Statistics show that, after adopting the method described in this invention, the progress payment review cycle for this project was shortened from an average of 7 working days under the traditional manual review model to 1 working day, significantly improving review efficiency. Simultaneously, due to the adoption of precise component-level quantity calculation and automatic comparison, the error rate in quantity calculation was reduced from ±8% under the traditional model to within ±1.5%, effectively avoiding problems such as false reporting of quantities and duplicate applications. Furthermore, each progress payment is precisely linked to a specific model component and acceptance time, achieving full-process data traceability and greatly improving the transparency and traceability of cost control. This practical application case fully demonstrates the significant technical effects of this invention in improving review efficiency, ensuring data accuracy, and strengthening risk management. Figure 4 This example illustrates a schematic diagram of the physical structure of an electronic device, which can be a smart terminal. Its internal structure diagram can be as follows: Figure 4As shown, the electronic device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements the acceptance-driven BIM model measurement and pricing method of any of the above embodiments.

[0084] Those skilled in the art will understand that Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present invention and does not constitute a limitation on the electronic device to which the present invention is applied. A specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0085] On the other hand, the present invention also provides a computer storage medium storing a computer program, which, when executed by a processor, implements the acceptance-driven BIM model measurement and pricing method of any of the above embodiments.

[0086] In another aspect, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium, and when the processor executes the computer instructions, it implements the acceptance-driven BIM model measurement and pricing method of any of the above embodiments.

[0087] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory.

[0088] By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0089] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0090] The above-described embodiments are merely illustrative of several implementations of the present invention, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of the invention. 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 modifications and improvements all fall within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the appended claims.

Claims

1. A BIM model measurement and pricing method based on acceptance-driven assessment, characterized in that, include: A three-dimensional building information model of a building project is obtained. In the building information model, the granularity of each model component is controlled to be no larger than the granularity of the on-site inspection batch. Each model component does not exist across inspection batches and is pre-set with measurement and pricing attribute information including at least the list code and quota code. It is also assigned a globally unique identifier and has a mapping relationship with the inspection batch code of the inspection batch to which it belongs. The acceptance data of each inspection batch is obtained through the mobile terminal acceptance system. The acceptance data includes at least the acceptance status of the inspection batch and the acceptance completion time automatically recorded by the system when the supervisor completes the acceptance operation on the mobile terminal acceptance system. According to the mapping relationship, the acceptance completion time is automatically linked to the corresponding model component as the actual completion time of the model component. When a certain inspection batch corresponds to multiple model components, the acceptance completion time of the inspection batch is simultaneously linked to the multiple model components. According to the preset measurement cycle, all model components whose actual completion time falls within the measurement cycle are selected from the building information model to form the set of components completed in this period; Based on the set of components completed in this period, the engineering quantity of each model component is automatically extracted, and the pricing amount of each component is automatically calculated according to the measurement and pricing attribute information, and the pricing amount of this period based on the BIM model is obtained. Obtain the application data submitted by the construction unit, compare the current period pricing amount based on the BIM model with the application data in multiple dimensions including at least the total amount, the quantity of each item of work and the unit price, and calculate the deviation rate under each dimension. The deviation rate is compared with a preset deviation threshold. If the deviation rate is less than or equal to the deviation threshold, the process is considered successful. Otherwise, an early warning is triggered and a difference analysis task is generated, requiring the submission of review materials. After review and confirmation, the process continues, and the final output includes the current pricing amount, declared amount, deviation rate, and difference details based on the BIM model.

2. The BIM model measurement and pricing method based on acceptance-driven approach according to claim 1, characterized in that, The control of the particle size of each model component to be no larger than the particle size of the field inspection batch includes: During the model creation phase, the model is divided according to the unified standards for construction quality acceptance of building engineering, so that individual model components do not exist across inspection batches, and each model component is pre-set with a unique identifier that is consistent with the inspection batch code of its respective batch.

3. The BIM model measurement and pricing method based on acceptance-driven approach according to claim 1, characterized in that, The process of obtaining acceptance data for each inspection batch through the mobile terminal acceptance system includes: The system receives acceptance data pushed by the acceptance system in JSON format via an open API interface. The JSON data includes at least the inspection batch code, acceptance status, acceptance completion time, and location code.

4. The BIM model measurement and pricing method based on acceptance-driven method according to claim 3, characterized in that, The step of automatically linking the acceptance completion time to the corresponding model component includes: Parse the inspection batch code in the JSON data, match the corresponding globally unique identifier of the model component according to the mapping database, and write the acceptance completion time into the actual completion time attribute field of the component. When a component is found to be without a timestamp attached, the system automatically marks it as a mapping anomaly and triggers a manual check.

5. The BIM model measurement and pricing method based on acceptance-driven approach according to claim 1, characterized in that, The step of selecting all model components from the building information model whose actual completion time falls within a preset measurement period, according to the preset measurement period, includes: The time filtering function in the building information modeling platform is invoked to extract all components whose actual completion time attribute values ​​fall within the range of the start and end times of the measurement period, forming a set of completed components for this period.

6. The BIM model measurement and pricing method based on acceptance-driven approach according to claim 1, characterized in that, The automatic extraction of the quantities of each model component includes: The system calls the API of the building information modeling platform to obtain the geometric parameters of the components, and automatically calculates the quantities of concrete, steel reinforcement, or formwork by combining them with the pre-set bill of quantities codes and corresponding quantity calculation rules. The calculation of the pricing amount includes automatically applying the corresponding unit price and fee rules according to the pre-set quota codes for summarization.

7. The BIM model measurement and pricing method based on acceptance-driven approach according to claim 1, characterized in that, The multi-dimensional comparison includes: The total amount, the quantity of each sub-item of work, and the unit price of each item in the bill of quantities are compared item by item, and the deviation rate is calculated for each dimension. The deviation rate is calculated according to the following formula: ； in, The corresponding value in the declared data. The value is calculated based on Building Information Modeling.

8. The acceptance-driven BIM model measurement and pricing method according to claim 1 or 7, characterized in that, The preset deviation threshold includes a multi-level threshold system: setting a first-level threshold, a second-level threshold, and a third-level threshold, wherein the first-level threshold is less than the second-level threshold, and the second-level threshold is less than the third-level threshold; when the deviation rate is within the range of the first-level threshold, it automatically passes; when the deviation rate exceeds the first-level threshold but is within the range of the second-level threshold, a yellow warning is triggered and a difference description requirement is generated; when the deviation rate exceeds the second-level threshold but is within the range of the third-level threshold, a red warning is triggered and the payment process is suspended, and on-site verification is mandatory.

9. The BIM model measurement and pricing method based on acceptance-driven approach according to claim 8, characterized in that, The triggering of the early warning and generation of the difference analysis task also includes: When the yellow or red alert is triggered, all associated model components are extracted to form a set of deviation components based on the list of items that caused the deviation. Retrieve the audit result data of each component in the deviation component set within the approved historical measurement period, the audit result data including the BIM calculated engineering quantity of each component within the historical period; The geometric parameters of each deviation component are obtained by calling the API of the building information modeling platform, and the total BIM engineering quantity of each component is calculated. The BIM calculated quantities of each component in the historical period are added together with the BIM calculated quantities in the current period. When the added value exceeds the total BIM quantity of the component, the component is marked as a duplicate application component. Extract the declared unit price of each item in the list associated with the deviation component set in the most recent three measurement periods. When the declared unit price of a certain item changes in the same direction for two consecutive measurement periods and the change exceeds a preset ratio, the item is marked as an item with abnormal unit price trend. In the aforementioned discrepancy analysis task, construction units are required to provide a recalculation draft of the engineering quantity for each duplicated component, and to provide a detailed analysis table of the unit price composition for each item in the list of abnormal unit price trends. Failure to provide these will result in the project not being approved.

10. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the acceptance-driven BIM model measurement and pricing method as described in any one of claims 1 to 9.

Images