BIM (Building Information Modeling)-based intelligent quantity calculation method and system for expressway

Abstract

The invention relates to the field of computer-aided highway engineering calculation, and discloses a BIM-based highway intelligent calculation method and system, and the method comprises the following specific steps: creating a highway engineering measurement modeling rule; creating a mapping matching rule of a BIM model component decomposition structure EBS, a bill of quantity structure BOQ and a project sub-item structure WBS; establishing a component measurement rule base; performing BIM modeling on a target project according to the measurement modeling rule, and endowing a calculation quantity attribute and a WBS attribute for a component; performing creation mode checking, calculation quantity attribute checking and WBS attribute checking on the target engineering BIM model; setting an engineering quantity list table style; embedding and writing list codes corresponding to the components, measurement rule identifiers and engineering quantity data obtained through calculation into the corresponding components of the BIM model in a structured attribute form; presetting the standard format of the 0 # ledger; therefore, reliable association between the list information and the model components is formed, and the value of the BIM in calculation amount and cost integrated application is fully exerted.

Description

Technical Field

[0001] This invention relates to the field of computer-aided quantity surveying in highway engineering, and specifically to a BIM-based intelligent quantity surveying method and system for highways. Background Technology

[0002] The compilation of bills of quantities and ledgers for traditional highway projects primarily relies on construction drawings from design institutes. Quantities are extracted manually from the drawings, and then manually categorized and summarized using spreadsheet tools such as Excel / WPS, in accordance with the measurement rules in the bidding documents and the format requirements for the bill of quantities and ledgers. Due to the large number of items in the bill of quantities for highway projects and the strong interdisciplinary nature of the work, differences in understanding of the drawings and measurement rules among different personnel can easily lead to calculation errors. To ensure the accuracy of the bill of quantities and ledgers, verification personnel often need to invest a significant amount of time in repeatedly reading drawings, calculating, and summarizing. This results in low ledger generation efficiency, poor coordination, and a high risk of error, further leading to disputes among various parties regarding the quantities.

[0003] With the development and application of BIM technology, mainstream BIM modeling software for highway engineering (such as OpenRoadsDesigner) can directly output bills of quantities for major materials. However, the existing output results generally suffer from problems such as fragmented table structure, inconsistent data definitions, and poor reusability. More importantly, the output quantities are usually the net physical quantities of model components, which are not strictly calculated according to the highway industry's measurement rules. Common rules such as hole deduction, intersection deduction, and priority are not fully considered, resulting in a mismatch between the BIM output quantities and the current highway industry measurement rules, affecting the consistency and auditability of bill of quantities preparation and measurement payment.

[0004] Furthermore, when conducting cost control based on BIM, the traditional approach typically requires manually entering or maintaining bill of quantities information into the BIM model as component attributes, and then performing cost analysis and control based on the model containing cost attributes. This method is cumbersome, prone to data errors, and makes it difficult to establish a reliable correlation between bill of quantities information and model components, thus failing to fully realize the value of BIM in integrated quantity surveying and cost estimation applications. Summary of the Invention

[0005] Based on the above description, this invention provides a BIM-based intelligent quantity calculation method and system for highways, which enables the rapid generation of bill of quantities and ledger No. 0 based on the BIM model, thereby improving the efficiency of bill of quantities and ledger No. 0 compilation; and establishes a reliable association between the bill of quantities information and model components, fully leveraging the value of BIM in the integrated application of quantity calculation and cost estimation.

[0006] On the one hand, the technical solution of the present invention to solve the above-mentioned technical problems is as follows: a BIM-based intelligent quantity calculation method for highways, comprising the following specific steps:

[0007] S01 creates a highway engineering measurement modeling rule to constrain the geometric type of components in the target project BIM model, and specifies the filling specifications for component information depth, quantity calculation attribute fields and WBS attribute fields, so that the geometry and attributes of the components can be parsed to generate engineering quantities and can be matched with the engineering quantity list sub-item feature items and the 0th ledger WBS structure tree.

[0008] S02 creates mapping and matching rules for the three components of the BIM model: Component Decomposition Structure (EBS), Bill of Quantities (BOQ), and Project Component Structure (WBS). The mapping and matching rules include at least: automatic mapping and association between EBS and BOQ based on text keywords of component layer names and / or attribute names, and three-way association between components in EBS, BOQ, and WBS based on the WBS attribute information written to the components.

[0009] S03 Establish a component measurement rule library, convert industry measurement rules into structured machine-readable rules and bind them to EBS component identifiers, and call the rule library during quantity calculation. Through Boolean operations, perform deduction judgment and deduction calculation in accordance with industry measurement rules for components with spatial intersection relationships.

[0010] S04 performs BIM modeling of the target project according to the measurement modeling rules and assigns quantity calculation attributes and WBS attributes to the components, and standardizes the layer name, attribute name and text keywords of the components according to the mapping matching rules.

[0011] S05 performs creation method verification, quantity calculation attribute verification, and WBS attribute verification on the target project BIM model. For components that fail the verification, a verification list is generated and the spatial location and attribute information of the corresponding components are automatically located in the modeling software.

[0012] After the verification is passed, S06 sets the bill of quantities table style, binds the components to the BOQ sub-items based on the mapping and matching rules of EBS and BOQ, calculates the component quantities according to the component measurement rule library, and outputs the bill of quantities according to the table style.

[0013] S07 embeds the corresponding list code, measurement rule identifier, and calculated quantity data of the component into the corresponding component of the BIM model in the form of structured attributes;

[0014] S08 presets the standard format of Ledger No. 0, extracts the WBS attributes of the components and the embedded list information and quantity data, and automatically matches the component WBS attributes with the WBS hierarchical structure of Ledger No. 0 based on the WBS keyword matching algorithm and establishes a mapping relationship. It then automatically fills in and exports the results of Ledger No. 0 according to the ledger format.

[0015] Through the above technical solutions, a closed-loop process is established, encompassing measurement modeling rules, EBS / BOQ / WBS three-structure mapping, a component measurement rule base, and model verification—list generation—list information write-back—automatic generation of ledger number 0. This ensures that the BIM model meets the requirements of "measurable, connectable, and traceable" from the source. This method transforms the traditional work of relying on manual drawing reading, classification and summarization, and repeated verification into rule-driven automated generation and consistency verification, significantly reducing omissions, recalculations, and inconsistencies caused by differences in human understanding. At the same time, through write-back and automatic ledger filling, secondary entry and repeated verification of the list and ledger are avoided, improving the efficiency and accuracy of the highway list and ledger outputs.

[0016] Based on the above technical solution, the present invention can be further improved as follows.

[0017] Furthermore, the component measurement rule base uses the EBS decomposition structure as the rule index framework, and establishes rule entries for each EBS component's unique identifier EID.

[0018] The rule entry shall include at least: rule number RID, rule version number Ver, effective time Te, applicable condition set Cond, parameter set Param, deduction priority Pr, and applicable metering object type identifier Type;

[0019] The parameter set Param includes at least: geometric calculation accuracy threshold ε, hole deduction threshold D0, and mapping score threshold τ;

[0020] The rule base sets traceability field constraints, requiring that at least each quantity calculation output is associated with the record RID, Ver, and Te, and can be traced back to the corresponding EID and the set of component identifiers involved in the deduction;

[0021] The dynamic update mechanism includes: performing a difference comparison on rule entries with the same RID but different Ver to determine the scope to be updated; batch binding the updated Cond and Param to the corresponding EID; retaining at least the previous version of the rule for traceability, and recording the rule update time, updater identifier, and modification log.

[0022] Through the above technical solution, rule entries are established using EBS as the index, and RID / Ver / Te, condition set Cond, parameter set Param, and traceability field constraints are introduced to ensure that each quantity calculation result can be clearly mapped to "which rule, which version, when it takes effect, and which component set it applies to". Compared with the pain points in the background of "calculation scope varies from person to person, making it difficult to recalculate and trace responsibility", this design realizes versioned management of rules and traceable recalculation, ensuring that the results of the same model are consistent under the same rule version. At the same time, the dynamic update mechanism enables the controllable positioning of the scope of impact and batch updates when the measurement rules change, avoiding the time cost and human re-verification burden caused by full recalculation.

[0023] Furthermore, the deduction determination and deduction calculation performed through Boolean operations includes: performing Boolean intersection operations on intersecting components to obtain a geometric intersection set and calculating the intersection quantity, wherein the intersection quantity is determined based on the measurement object according to volume, area or length;

[0024] Set a geometric calculation accuracy threshold ε. When the intersection amount is not greater than ε, it is judged as an invalid intersection and no deduction is performed.

[0025] When the intersection is greater than ε, the deduction rule bound to the EID of the deducted component is invoked, and the key parameters of the deducted component are verified according to the applicable condition set Cond. If the verification passes, Boolean difference operation is performed and deduction is performed according to the difference set. If the verification fails, the original quantity of the project is maintained.

[0026] When the same deducted component intersects with multiple deducted components at the same time, the components are deducted in descending order of deduction priority Pr, and the intermediate results after each deduction are cumulatively updated.

[0027] The deduction process records traceability information, including at least: the identifier of the deducted component, the identifier of the deducted component, the intersection quantity, the RID and Ver used, the determination result of whether the deduction is effective, and the net quantity result after deduction.

[0028] Through the above technical solution, Boolean intersection / difference operations, combined with geometric precision threshold ε, applicable condition verification, and deduction priority Pr, achieve a verifiable calculation link that "deducts only for valid intersections, deducts according to the rules, and avoids duplicate deductions caused by multiple component intersections." This solution addresses the problems of "manual deductions being prone to omissions, duplicate deductions, and difficult reproducibility" by using ε to filter modeling errors and minor overlapping noise, using Cond to constrain the deduction effectiveness conditions, and using Pr to ensure consistent deduction order when multiple components intersect, thereby improving deduction accuracy and recalculation consistency. It also records the intersection quantity and effectiveness judgment results, reducing audit and verification costs.

[0029] Furthermore, the industry measurement rules include a hole deduction threshold rule, and define the hole equivalent size parameter D and the threshold D0;

[0030] When D is not greater than D0, the hole is not included in the quantity deduction; when D is greater than D0, the hole is deducted according to the amount of intersection formed with the component to be deducted.

[0031] The equivalent size parameter D of the hole is calculated from the geometric parameters of the hole, and the geometric parameters include at least one of the hole diameter, the short side of the hole, the long side of the hole, or the cross-sectional area of ​​the hole.

[0032] The threshold D0 is written into Param as a configurable parameter of the rule base and can be set with different values ​​according to the component type Type.

[0033] The hole deduction result is written into the traceability field, which includes at least the hole component identifier, D value, D0 value, whether deduction is performed, and the RID and Ver used.

[0034] The above technical solution sets configurable deduction rules for the equivalent size D of the hole and the threshold D0, ensuring that hole deductions are consistent with industry measurement standards and can be configured differently according to component type. This solution addresses the problem of "manual judgment of whether to deduct holes and errors caused by inconsistent interpretation of standards" in the background: when D≤D0, it automatically determines not to deduct, avoiding frequent Boolean operations and statistical noise caused by small holes; when D>D0, it deducts according to the intersection quantity, ensuring accurate deduction of large holes; during the deduction process, D / D0 and the adopted RID / Ver are written into the traceability field, facilitating rapid review and consistency verification of disputed holes, thereby improving the accuracy and auditability of engineering quantities.

[0035] Specifically, in Boolean deduction cases, for items in the bill of quantities that need to be deducted, the software automatically determines the deduction conditions and deducts or does not measure components that meet the conditions; for example, if the volume of concrete occupied by pipes, steel bars, anchors, etc. with a diameter greater than 200mm needs to be deducted, the software will automatically determine the model that has a volume collision with the concrete and determine whether its diameter attribute exceeds 200mm. If it does, its volume will be automatically deducted.

[0036] Furthermore, the mapping matching rules include a keyword dictionary Dict, a matching weight parameter W, a matching score threshold τ, a matching priority Level, a mutual exclusion table Mutex, and an exception list ExList;

[0037] Extract keyword sets from the layer names and / or attribute names of components, and match and score them with the feature item keyword sets of candidate BOQ sub-items. The scoring results are used to determine whether to establish a mapping association between EBS and BOQ.

[0038] When the score of a candidate BOQ sub-item is not less than the threshold τ, a mapping association is established. When multiple candidate BOQ sub-items meet the threshold at the same time, a unique mapping result is determined according to the priority level.

[0039] Set a unique attachment constraint: Except for component types belonging to the exception list ExList, the same component is only allowed to attach one BOQ sub-item code and one WBS node code at the same time;

[0040] Set up a conflict handling mechanism: When the same component is mapped to multiple BOQ sub-items or multiple mutually exclusive WBS nodes defined in the Mutex table, output a conflict record and mark the component as "to be reviewed" to block automatic summary output;

[0041] The conflict record must include at least the following fields: unique component identifier, candidate target list, respective score, priority, mutual exclusion basis, trigger time, and processing status, to meet the requirements of verifiability and traceability.

[0042] Through the above technical solution, the keyword dictionary Dict, weight W, scoring threshold τ, priority Level, mutual exclusion table Mutex, and exception list ExList upgrade the linking of components to BOQ / WBS from "manual item matching" to an automatic matching mechanism of "quantifiable scoring + conflict prevention". This solution directly addresses the problems of "many sub-items, large differences in human interpretation, and difficulty in detecting incorrect item matching" in the background: τ controls the mapping confidence, Level determines the unique result among multiple candidates, and mutual exclusion constraints prevent the same component from being incorrectly linked to multiple mutually exclusive sub-items / nodes; conflicting components are automatically marked "to be reviewed" and records are output, reducing errors entering the summary table and reducing the systematic deviation between the list and the ledger from the source.

[0043] Furthermore, the model verification includes at least the verification of the creation method, the verification of the computational quantity attribute, and the verification of the WBS attribute;

[0044] The verification of the creation method includes at least: whether the component geometry type conforms to the metrological modeling rules, whether the component has abnormal geometry such as non-closed body or self-intersection, and whether the component meets the minimum measurable scale threshold.

[0045] The verification of the quantity calculation attributes includes at least: whether the required quantity calculation fields are complete, whether the field types and value ranges meet the preset constraints, whether the unit of measurement is consistent with the unit of the list item, and whether the key threshold parameters are correctly inherited or filled in.

[0046] The WBS attribute verification includes at least: whether the WBS code exists, whether the coding level meets the layer depth constraint parameter H, whether the code and component type meet the consistency constraint, and whether the unique attachment constraint is met.

[0047] Output a checklist and support automatic location of failed components in the modeling software. The checklist shall include at least the component's unique identifier, problem type, spatial coordinates, missing or abnormal field name, current field value, and reference to the suggested repair rule entries.

[0048] The traceability fields for the verification and repair process records should include at least the attribute differences before and after repair, the repairer's identifier, and the repair time.

[0049] Through the above technical solutions, the creation method verification, quantity calculation attribute verification, and WBS attribute verification are implemented, and problematic components are automatically located in the modeling software, achieving executable control of "quality pre-positioning." This solution addresses the problem in the background of "non-standard models / attributes leading to repeated rework in subsequent quantity calculations and time-consuming verification": the creation method verification filters abnormal geometry and components that do not meet the minimum measurable scale; the quantity calculation attribute verification ensures that required fields, units, and threshold inheritance are correct; the WBS verification uses the hierarchical depth parameter H and unique attachment constraints to ensure that the ledger can be automatically matched; the verification list provides component identification, coordinates, and repair references, shortening the location and rework time, and recording repair differences and personnel time, improving the stability of results and management traceability.

[0050] Furthermore, the bill of quantities table style shall at least limit the field set, field order, field format constraints, and unit of measurement consistency constraints;

[0051] While outputting the bill of quantities, a reverse association index is established so that the corresponding set of components can be retrieved for any item code and item name in the bill of quantities.

[0052] The component record of the reverse association index includes at least: component unique identifier, bill of quantities item code, bill of quantities item name, adopted measurement rule identifier RID, rule version number Ver, key parameter summary and calculation result quantity;

[0053] Set a unique attachment constraint verification: For non-exceptional list ExList components, if multiple list item codes are detected for the same component, an attachment exception record will be output and the component will be blocked from participating in the list summary.

[0054] When a discrepancy is detected between the unit of measurement of a component and the unit of measurement of a sub-item in the bill of quantities, the unit is converted according to the preset unit conversion table or an inconsistency alarm is output and the automatic summarization of that sub-item is blocked.

[0055] Each sub-item summary row of the bill of quantities shall record traceability fields, including at least the number of components involved in the summary, the component identifier list reference, the rule version information used, and the generation timestamp.

[0056] Through the above technical solution, a bill of quantities output mechanism is achieved by pre-setting the bill of quantities table style, reverse association index, unique attachment verification, and unit consistency processing, thus realizing "unified output format + component lookup capability". This solution addresses the problems of "inconsistent manual summary format and difficulty in tracing back to drawings / models" in the background: the field set and order ensure that the exported data meets the bidding / measurement requirements; the reverse index supports quick retrieval of the participating component set from any bill of quantities sub-item, reducing the review cost; multiple attachments and inconsistent units are automatically blocked or converted to avoid incorrect summarization into the final bill of quantities; each sub-item summary row records the component quantity, version, and timestamp, making the bill of quantities verifiable, recalculateable, and auditable.

[0057] Furthermore, the automatic generation of ledger 0 includes establishing a mapping relationship Map of "component unique identifier - ledger WBS node", and automatically summarizing and filling the component engineering quantity under the same WBS node according to the mapping relationship;

[0058] The No. 0 ledger adopts a preset standard format, which includes at least WBS level fields, list item fields, unit of measurement fields, quantity fields, and source traceability fields.

[0059] The source tracing fields include at least: associated component set reference, list item code, rule number RID, rule version number Ver, mapping rule version identifier and generation timestamp;

[0060] The linked update includes an incremental update mechanism: when the quantity or list information of any component changes, only the ledger record corresponding to the WBS node to which the component belongs is updated incrementally, and the update time identifier and source traceability field are updated synchronously.

[0061] When the component mapping relationship changes, first perform mapping change verification and output a change list. The change list should include at least the changed component identifier, the original WBS node, the new WBS node, the reason for the change, and the effective time. Then, recalculate or incrementally correct the affected WBS nodes.

[0062] The process of exporting ledgers should record export traceability information, including at least the export format, export file identifier, exporter identifier, and export time.

[0063] Through the above technical solution, a "component-ledger WBS node" mapping map is established, a standard format for Ledger 0 is preset, and an incremental update mechanism is implemented, enabling Ledger 0 to be automatically generated from the BIM model and kept consistent with changes. This solution directly addresses the problem of "Ledger 0 relying on manual classification and summarization in Excel, leading to low efficiency due to repeated reading and verification of drawings" in the background: automatic summarization and filling by WBS node reduces manual input and secondary verification; the source traceability field solidifies the component set, list code, RID / Ver, and mapping version, facilitating audit accountability; incremental updates only recalculate affected WBS nodes, avoiding full recalculation and repeated verification, making it particularly suitable for highway projects with frequent design changes, significantly improving the efficiency and consistency of ledger preparation.

[0064] Secondly, the technical solution of the present invention to solve the above-mentioned technical problems is as follows: A BIM-based intelligent quantity calculation system for highways, comprising:

[0065] The rule configuration module is used to configure metrological modeling rules, configure EBS / BOQ / WBS three-structure mapping and matching rules, and establish a component metrological rule library bound to EBS component identifiers;

[0066] The modeling and attribute management module is used to constrain modeling according to quantitative modeling rules and batch assign quantity calculation attributes and WBS attributes, while standardizing component layer names and / or attribute name keywords according to mapping matching rules.

[0067] The model verification module is used to perform verification of creation method, quantity calculation attribute and WBS attribute, generate verification list and drive the modeling software to automatically locate non-compliant components;

[0068] The quantity calculation and bill of quantities generation module is used to bind components to BOQ sub-items based on mapping matching rules, and call the component measurement rule library to perform deduction judgment and quantity calculation in combination with Boolean operation. It generates and exports the bill of quantities according to the preset bill of quantities table style, and writes the bill of quantities code, measurement rule identifier and quantity data into the corresponding component as structured attributes.

[0069] The No. 0 ledger generation module is used to automatically match the WBS attributes of components with the WBS hierarchical structure of No. 0 ledger based on the WBS keyword matching algorithm, automatically fill in the ledger format to generate No. 0 ledger, and then export it.

[0070] The data storage and interaction module is used to centrally store rule data, model data, verification results, list data, and ledger data, and provides data interaction interfaces between modules.

[0071] Through a modular system architecture encompassing rule configuration, modeling and attribute management, model verification, quantity calculation and bill of quantities generation, ledger generation (number 0), and data storage interaction, an integrated automated quantity calculation platform integrating "rules—models—deliverables" is achieved. This system consolidates the previously scattered workflows between modeling software, Excel, cost estimation software, and manual verification into a unified process. This ensures reusable rule configurations, controllable model quality, and automatic and traceable bill of quantities / ledgers generation. Centralized data storage and inter-module interfaces reduce errors and version inconsistencies caused by manual data handling, improve team collaboration efficiency, and provide a structured data foundation for subsequent auditing, recalculation, and change comparison, thereby enhancing the overall industrialization level of quantity calculation and deliverables.

[0072] Furthermore, the quantity calculation and bill of quantities generation module includes a rule-bound deduction calculation engine and a bill of quantities information write-back unit, wherein:

[0073] The deduction calculation engine bound to the rule is used to call the component measurement rule library entries bound to it using the unique identifier `EID` of the EBS component as an index, and to determine the validity of the geometric interaction of intersecting components based on the rule parameter threshold; when the validity determination is met, a Boolean intersection operation is performed on the intersecting components to obtain the intersection set and the intersection quantity is calculated, and a Boolean difference operation is performed on the deducted component to obtain the net quantity after deduction when the rule application conditions are met; when the same deducted component corresponds to multiple deducted components, the deductions are performed sequentially according to the deduction priority in the rule entries and the cumulative updates are performed.

[0074] The measurement rules are formed in accordance with relevant specifications and standards, and include: calculation formulas and deduction rules;

[0075] The list information write-back unit is used to write the list item code, list item name, adopted measurement rule number RID and rule version number Ver, quantity before deduction, net quantity after deduction, and deduction traceability information of the component to the structured attribute fields of the corresponding BIM component.

[0076] The No. 0 ledger generation module establishes a mapping relationship between "component unique identifier - ledger WBS node" based on the structured attribute fields and WBS attributes. When the component quantity or list information changes, it only performs incremental updates on the affected WBS nodes and outputs a traceability field containing rule version information.

[0077] By employing an "attribute-geometric association unit + Boolean operation engine," the design ensures a one-to-one correspondence between component attributes and 3D geometry, enabling stable deduction calculations. "Access control + log management" ensures controllable operations and traceable accountability in multi-user collaboration. This design addresses the risks of "difficult-to-reproduce results" and "accidental modification of rules / models due to multiple users": the quantity calculation engine calls rules based on EID and determines valid intersections according to thresholds, ensuring consistent deduction criteria; the bill of quantities write-back forms a "component-rule-bill of quantities-quantity" link, reducing the disconnect between the bill of quantities and the model; and access control and logging trace the rule creation, model modification, quantity calculation, and export processes, facilitating auditing and accountability, and reducing quality fluctuations caused by unauthorized changes to results.

[0078] Compared with the prior art, the technical solution of this application has the following beneficial technical effects:

[0079] 1. Achieve a "rule-driven integrated automatic quantity calculation closed loop," significantly improving efficiency and accuracy. Through measurement modeling rules, EBS / BOQ / WBS three-structure mapping, rule-based measurement, and model verification, the traditional process of "manual map reading—manual classification and summarization—repeated verification" is replaced by a closed loop of "analyzable modeling—verifiable mapping—executable quantity calculation—automatic generation of lists and ledgers." The core effect is to move the source of error forward to the modeling and rule layer for constraint and verification, reducing omissions, recalculations, and incorrect itemizations caused by differences in human understanding. It also transforms the generation of lists and ledgers from a manual-intensive process to automated output, thereby achieving stable efficiency and consistency improvements in scenarios with numerous sub-items and complex statistics, such as highways.

[0080] 2. Based on industry norms, standards, and national standards, calculation rules are formulated; engineering quantities conforming to these rules are generated, along with deduction rules and calculation formulas, ensuring consistency in industry measurement standards; measurement rule entries are bound using EBS component identifiers as indexes, incorporating RID / Ver / Te versioning, Cond / Param thresholding, and Boolean intersection / difference operations for validity determination (ε, hole threshold D0, deduction priority Pr, etc.), achieving standardization and verifiability of the deduction process. The core effect is: engineering quantity results are repeatable and interpretable under the same model and rule version; in the face of high-error points such as multi-component intersections and hole deductions, duplicate or missed deductions are avoided, and traceability information such as intersection quantities, determination results, and rule versions used is solidified, significantly reducing verification and auditing costs.

[0081] 3. The "List of Items - Components - Ledger" are linked one-to-one and incrementally updated to ensure consistent results and adapt to frequent changes. The list of items codes, measurement rule identifiers, gross / net quantities and traceability information are structured and written back to the components. A reverse index of the list of items and a WBS mapping map for the ledger are established. When the quantity of a component or the mapping changes, only the affected WBS nodes are updated incrementally. The core effect is that the list of items and Ledger No. 0 no longer rely on secondary input and manual comparison. The results are consistent and the source of the component can be traced back from any item in the list of items. At the same time, in highway projects with frequent design changes, full recalculation and repeated verification are avoided, and the engineering delivery capability of "partial update and global consistency" is achieved.

[0082] 4. Through the data storage and interaction module, centralized management and interface decoupling of rules, models, lists, and ledgers are achieved, connecting the entire process of "modeling-quantity calculation-cost / construction" into a single data source. This supports multi-disciplinary collaboration and result reuse among design, cost, and construction professionals, significantly reducing the deviation of manual transcription of attribute and list data. At the same time, an incremental update mechanism is introduced, so when the quantity of component work or mapping relationship changes, only the affected WBS nodes are partially recalculated, avoiding the high cost of full recalculation and improving the efficiency of change response. Furthermore, by solidifying rule versions and responsible parties through traceability fields, deduction details, and operation logs, the quantity calculation process is made traceable, verifiable, and auditable, meeting the compliance requirements of measurement, payment, and auditing and reducing the risk of disputes. Attached Figure Description

[0083] Figure 1 This is a flowchart of the BIM-based intelligent quantity calculation method for highways according to the present invention.

[0084] Figure 2 This is a block diagram of the overall structure of the BIM-based intelligent quantity calculation system for highways according to the present invention.

[0085] Figure 3 This is a schematic diagram of the EBS / BOQ / WBS three-structure and mapping matching relationship of the present invention;

[0086] Figure 4 This is a schematic diagram illustrating the metrological modeling rules and component attribute field specifications of the present invention;

[0087] Figure 5 This is a schematic diagram of the component measurement rule base data structure and version management of the present invention;

[0088] Figure 6 This is a schematic diagram of the model verification and automatic positioning correction process of the present invention;

[0089] Figure 7 This is a schematic diagram of the Boolean deduction calculation engine of the present invention;

[0090] Figure 8This is a schematic diagram of the bill of quantities generation, export, and write-back mechanism of the present invention.

[0091] Figure 9 This is a schematic diagram of the automatic generation and incremental update process of ledger number 0 of the present invention;

[0092] Figure 10 This is a schematic diagram of the overall system structure and deployment configuration of the present invention;

[0093] Figure 11 This is a block diagram of the system modules of the present invention;

[0094] Figure 12 This is a schematic diagram of the rule configuration module subunit structure of the present invention;

[0095] Figure 13 This is a flowchart illustrating the modeling and attribute management plugin workflow of the present invention.

[0096] Figure 14 This is a flowchart of the model verification and automatic location reverse lookup process of the present invention;

[0097] Figure 15 This is a schematic diagram of the attribute-geometric association and spatial index structure of the present invention;

[0098] Figure 16 This is a flowchart of the deduction determination and Boolean operation net amount calculation of the present invention;

[0099] Figure 17 This is a data link diagram for inventory generation, write-back, and export in this invention;

[0100] Figure 18 This is a flowchart illustrating the consistency of ledger No. 0 generation and incremental update in this invention.

[0101] Figure 19 This is a schematic diagram of the data storage and interaction module, permissions, and log structure of the present invention;

[0102] Figure 20 This is the BOQ-EBS keyword matching interface;

[0103] Figure 21 Configure the interface for the bill of quantities;

[0104] Figure 22 Write the calculated bill of quantities back into the BIM model;

[0105] Figure 23 This is an interface for matching and binding BIM model attribute data with WBS keywords.

[0106] Figure 24 This is an interface showing the matching results between BIM model attribute data and WBS keywords;

[0107] Figure 25 Export interface for ledger number 0. Detailed Implementation

[0108] To facilitate understanding of this application, a more complete description will be provided below with reference to the accompanying drawings, which illustrate embodiments of the present application. However, the present application can be implemented in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided so that the disclosure of this application will be thorough and complete.

[0109] 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 application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

[0110] Terminology definitions / symbol explanations:

[0111] EBS (Element Breakdown Structure): BIM model component decomposition structure refers to the model structure system formed by hierarchically decomposing engineering entities in a BIM model according to component type, functional attributes, and structural level;

[0112] BOQ (Bill of Quantities): The bill of quantities structure for highway engineering projects refers to the bill of quantities system used for project pricing and measurement, which is divided into "chapter-section-item" levels according to the highway engineering bill of quantities measurement specifications.

[0113] WBS (Work Breakdown Structure): The project work breakdown structure refers to the hierarchical project structure system that divides a highway engineering project into sub-items according to the implementation stage and engineering parts. Its hierarchical structure is consistent with the hierarchical structure of the highway engineering ledger No. 0.

[0114] Quantitative modeling rules: geometric type constraints, information depth, attribute fields, layer / naming / keyword specifications;

[0115] Measurement rule base: Structured rules bound to EBS identifiers (including threshold deduction, cross-deduction priority, conditional logic, version update, component quantity calculation formula, and component quantity unit);

[0116] Ledger No. 0: A template for a measurement ledger summarized according to the WBS hierarchy;

[0117] Boolean operations: intersection is used for intersection determination, and difference is used for deduction calculation.

[0118] Example 1:

[0119] refer to Figures 1-9 A BIM-based intelligent quantity calculation method for highways includes the following specific steps:

[0120] S01 creates a highway engineering measurement modeling rule to constrain the geometric type of components in the target project BIM model, and specifies the filling specifications for component information depth, quantity calculation attribute fields and WBS attribute fields, so that the geometry and attributes of the components can be parsed to generate engineering quantities and can be matched with the engineering quantity list sub-item feature items and the 0th ledger WBS structure tree.

[0121] S02 creates mapping and matching rules for the three components of the BIM model: Component Decomposition Structure (EBS), Bill of Quantities (BOQ), and Project Component Structure (WBS). The mapping and matching rules include at least: automatic mapping and association between EBS and BOQ based on text keywords of component layer names and / or attribute names, and three-way association between components in EBS, BOQ, and WBS based on the WBS attribute information written to the components.

[0122] S03 Establish a component measurement rule library, convert industry measurement rules into structured machine-readable rules and bind them to EBS component identifiers, and call the rule library during quantity calculation. Through Boolean operations, perform deduction judgment and deduction calculation in accordance with industry measurement rules for components with spatial intersection relationships.

[0123] S04 performs BIM modeling of the target project according to the aforementioned measurement modeling rules and assigns quantity calculation attributes and WBS attributes to the components. In addition, according to the aforementioned mapping matching rules, the layer name, attribute name and text keywords of the components are standardized so that each component can be linked to BOQ sub-items and WBS nodes.

[0124] S05 verifies the creation method, quantity calculation attributes, and WBS attributes of the target project BIM model. For components that fail the verification, it generates a verification list and automatically locates the spatial position and attribute information of the corresponding components in the modeling software to support correction.

[0125] After the verification is passed, S06 sets the bill of quantities table style, binds the components to the BOQ sub-items based on the mapping and matching rules of EBS and BOQ, calculates the component quantities according to the component measurement rule library, and outputs the bill of quantities according to the table style.

[0126] Prioritize the verification of creation method, quantity calculation attribute and WBS attribute, and verify the mapping matching rules after they are passed. Verify whether the "layer name, attribute name and text keywords of the component" have been standardized.

[0127] S07 embeds the corresponding list code, measurement rule identifier and calculated engineering quantity data of the component into the corresponding component of the BIM model in the form of structured attributes, so as to realize the one-to-one mapping association between list information and components.

[0128] S08 presets the standard format of Ledger No. 0, extracts the WBS attributes of the components and the embedded list information and quantity data, and automatically matches the component WBS attributes with the WBS hierarchical structure of Ledger No. 0 based on the WBS keyword matching algorithm and establishes a mapping relationship. It then automatically fills in and exports the results of Ledger No. 0 according to the ledger format.

[0129] The execution entity in this embodiment can be quantity calculation software (including modeling software plugins / interfaces) deployed on a server or engineer's workstation, which includes at least: a quantity calculation modeling rule management module, an EBS / BOQ / WBS mapping module, a quantity calculation rule base module, a model verification module, a Boolean deduction quantity calculation engine, a result export module and write-back module, and a zero-ledger generation and incremental update module. Each module is linked through a unified component unique identifier (e.g., GUID) and a database index field.

[0130] As a preferred method, S01 creates highway engineering measurement modeling rules. During the project initialization phase, "measurement modeling rules" are established to constrain the geometric types and attribute filling specifications of components in the target project's BIM model. Specifically, this includes:

[0131] Geometry type constraints: Preset measurable geometry set TypeSet, such as solid extrusion, sweep, loft, closed solid, smart solid and parametric solid, etc.; non-closed solid, self-intersecting facets, zero thickness and other abnormal geometry are set as non-compliant;

[0132] Information Depth and Field Specifications: The information depth of components shall not be lower than the preset level L (e.g., to meet the requirement of extracting three types of measurements: length, area, and volume); establish a set of calculation attribute fields QFields (e.g., measurement object type Type, measurement unit Unit, material / strength grade, whether to participate in deduction, hole type, etc.) and a set of WBS attribute fields WFields (e.g., WBS code, level, node name keywords, etc.);

[0133] Parsable and Matchable Constraints: Require the component geometry and attributes to meet the minimum conditions for generating the engineering quantity analytically, while ensuring that it can be matched with the BOQ sub-item feature item keywords and the WBS structure tree node of ledger number 0.

[0134] Preferably, S02 creates mapping and matching rules for EBS, BOQ, and WBS. To achieve consistent linking of "component - list item - ledger WBS", this embodiment establishes mapping and matching rules that include at least:

[0135] Dict Keyword Dictionary: Creates synonyms and abbreviations for common highway components and inventory items (e.g., "bridge abutment / body", "roadbed filling / fill", "guardrail / wave beam", etc.).

[0136] Matching score and threshold τ: Extract the keyword set Kc from the component layer name and / or attribute name, and calculate the score Score with the keyword set Kb of the candidate BOQ sub-item feature items; the example is weighted matching:

[0137] Score = Σ (w_i · match_i), where match_i∈{0,1} indicates whether the i-th keyword is matched, and w_i is the weight parameter W;

[0138] When Score ≥ τ (e.g., τ = 0.75), establish the mapping between EBS and BOQ.

[0139] Priority Level and Unique Attachment Constraint: When multiple candidate sub-items simultaneously meet the threshold, the unique result is determined by the Level; except for the component types in the exception list ExList, the same component is only allowed to attach one BOQ code and one WBS node code at the same time.

[0140] Mutex and Conflict Handling: If a component is mapped to a mutually exclusive sub-item or mutually exclusive WBS node defined by the Mutex, a conflict record is generated and marked "pending review", preventing it from participating in the automatic summary output; the conflict record must include at least the component's unique identifier, candidate target list, score, priority, mutual exclusion basis, trigger time, and processing status.

[0141] Three-way association mechanism: After writing the WBS code / node information into the component WBS attribute field, the component is associated in three directions with EBS, BOQ and WBS, ensuring that the subsequent list and ledger can be looked up to the component set.

[0142] As a preferred approach, S03 establishes a component measurement rule base and binds it to EID, transforming industry measurement rules into structured, machine-readable rule entries, and using EBS as the index framework. Specifically:

[0143] Rule Index and Entry Structure: A rule entry is established for each EBS component with a unique identifier EID. The entry includes at least: rule number RID, version number Ver, effective time Te, applicable condition set Cond, parameter set Param, deduction priority Pr, and applicable metering object type Type.

[0144] Examples of key parameter Param: geometric calculation accuracy threshold ε (e.g., volume class ε=1e-6 m³ or configured according to project accuracy); hole deduction threshold D0 (e.g., D0=0.05 m or configured according to Type); mapping score threshold τ; unit consistency check parameter U; WBS level depth constraint parameter H (e.g., H=5).

[0145] Traceability field constraints: Each output quantity result must be associated with RID, Ver, and Te, and can be traced back to EID and the set of component identifiers involved in the deduction.

[0146] Dynamic update mechanism: For rules with the same RID but different Ver, the differences are compared, the update scope is determined, and the rules are batch bound to the corresponding EID; at least the previous version of the rules are retained for traceability, and the update time, updater identifier and modification log are recorded.

[0147] Preferably, S04 completes BIM modeling according to the rules and standardizes naming and attributes. In the modeling software, a BIM model of the target project is established according to the rules in S01, and quantity calculation attributes and WBS attributes are assigned to the components. To improve the success rate of automatic mapping, this embodiment standardizes layer names, family / type names, and key attribute names:

[0148] For example, components such as "pier cap", "pier body" and "cap beam" can be placed into preset layers / categories, and the Type, material grade and unit of measurement can be written in the attributes;

[0149] At the same time, WBS codes (such as "subgrade engineering / fill section / ... / sub-item") are written for the components to ensure that they can be directly attached to WBS nodes.

[0150] After standardization, each component can be linked to the BOQ sub-item and the WBS node.

[0151] As a preferred method, S05 model verification and automatic positioning correction perform three types of verifications on the target project BIM model:

[0152] Creation method verification: Check whether the geometry type is in the TypeSet; whether there are non-closed bodies, self-intersections, or abnormal geometry; and whether the minimum measurable scale threshold is met.

[0153] Quantity calculation attribute verification: Check whether the required fields are complete; whether the field type / value range meets the preset constraints; whether the component measurement unit is consistent with the unit of the sub-item to be attached; and whether the key thresholds are correctly inherited or filled in.

[0154] WBS attribute verification: Check if the WBS code exists; whether the level meets the H requirement; whether the code and component type are consistent; and whether the unique attachment constraint is met.

[0155] For components that fail the verification, a verification list is generated. The list must include at least: the component's unique identifier, the problem type, spatial coordinates, missing / abnormal field names, current field values, and the rule entries (RID / Ver) referenced for suggested repair. Simultaneously, the corresponding component's spatial location and attribute panel are automatically located via the modeling software API / plugin, enabling engineers to quickly correct the issue. The repair process records the differences before and after repair, the repairer's identifier, and the repair time.

[0156] As a preferred option, the S06 bill of quantities table style settings, automatic binding, and quantity calculation output are executed after verification to generate the bill of quantities:

[0157] Table style definition: Preset the set of fields in the bill of quantities, field order, format constraints and unit of measurement consistency constraints (e.g., "sub-item code - name - characteristic - unit - quantity - source traceability").

[0158] Components are bound to BOQ sub-items: Components are bound to BOQ sub-item codes according to the S02 mapping rules; conflicting or pending-review components are not included in the automatic summary.

[0159] Boolean deduction calculation (in conjunction with S03 rule base):

[0160] Perform Boolean intersection operation on components that have spatial intersection relationship to obtain the intersection set, and calculate the intersection quantity (volume / area / length is determined according to the object being measured);

[0161] When the intersection amount is ≤ ε, it is determined to be an invalid intersection and no deduction is made; when the intersection amount is > ε, the deduction rule bound to the EID of the deducted component is called. If the Cond verification passes, the Boolean difference operation is performed and the amount of the difference is deducted; otherwise, the original amount is kept.

[0162] When the same deducted component intersects with multiple deducted components, deducting them sequentially from high to low according to Pr, and updating the intermediate results cumulatively;

[0163] The entire process records and traces information, including: the identifier of the deducted component, the identifier of the deducted component, the intersection quantity, the RID / Ver used, whether the deduction is effective, and the net quantity after the deduction.

[0164] Example of a threshold rule for hole deduction: Determining the equivalent size D of the hole relative to the threshold D0:

[0165] When D ≤ D0, the hole is not included in the deduction; when Deduct based on the intersection amount;

[0166] D can be calculated from the cross-sectional area A of the hole, for example Alternatively, the equivalent value can be obtained from the long / short side of the rectangular hole;

[0167] The deduction result is written to the traceability fields: hole component identifier, D, D0, whether deduction is applied, and RID / Ver.

[0168] Reverse association index: When outputting the list, an index for "sub-item code → component set" is created. The index record includes at least the component's unique identifier, sub-item code, RID / Ver, key parameter summary, and quantity result. If multiple sub-item codes corresponding to the same component are detected and are not in ExList, an attachment anomaly is output and the component is blocked from participating in the summary. If the units are inconsistent, the conversion is performed according to the unit conversion table or an alarm is output and automatic summary is blocked.

[0169] Finally, export the bill of quantities in a table format, and record the number of participating components, the component identifier list reference, the rule version information used, and the generation timestamp in the summary row of each sub-item.

[0170] Preferably, the S07 bill of quantities information and quantity results are written back to the BIM components. To achieve "model as result, result traceability", this embodiment writes back the bill of quantities code, measurement rule identifier and calculated quantity of the component to the BIM model component in the form of structured attributes:

[0171] For example, add a new "BOQ_Info" attribute group to the component attribute set and write: BOQ code, RID, Ver, Te, quantity Qty, unit of measurement Unit, generation timestamp, and deduction summary (such as reference to the list of components involved in the deduction).

[0172] After writing back, a one-to-one mapping between the list information and the components is achieved, and the basis for calculation can be directly traced back to the components in subsequent audits, changes, and payment measurements.

[0173] As a preferred option, S08: Automatic generation and incremental update of ledger number 0, based on the preset standard format of ledger number 0, performs ledger generation:

[0174] Templates and Fields: The standard ledger format should include at least WBS level fields, list item fields, unit of measurement fields, quantity fields, and source traceability fields; the source traceability fields should include at least the associated component set reference, list code, RID / Ver, mapping rule version identifier, and generation timestamp.

[0175] Establish a mapping relationship Map: Extract the component WBS attributes and the list information and quantity data written back by S07. Based on the WBS keyword matching algorithm, automatically match the component WBS attributes with the ledger WBS structure tree to form a mapping relationship Map of "component unique identifier - ledger WBS node"; output a list to be reviewed for components that cannot be matched or whose mutual exclusion rules are not met.

[0176] Automatic summary and filling: Based on the Map, the component quantities under the same WBS node are summarized by bill of quantities item, the ledger is automatically filled and exported.

[0177] Linked update and incremental mechanism: When the quantity or bill of quantities information of any component changes, only the ledger record No. 0 corresponding to the WBS node to which the component belongs is updated incrementally, and the update time identifier and source traceability field are updated at the same time; when the mapping relationship changes, the mapping change verification is performed first and the change list is output (change component identifier, original WBS node, new WBS node, reason for change, effective time), and then the affected nodes are recalculated or incrementally corrected; record export traceability information: export format, export file identifier, exporter identifier, export time.

[0178] This embodiment solidifies the data foundation of "calculable, matchable, and traceable" through measurement modeling rules during the modeling stage; in the quantity calculation stage, it realizes net quantity calculation in accordance with industry measurement rules through rule base versioning and Boolean deduction mechanism; in the results stage, it realizes consistent linkage between the list, No. 0 ledger and components through list write-back and ledger Map mapping, and supports incremental updates and audit traceability of subsequent changes, thereby significantly reducing the cost of manual drawing interpretation and repeated calculation, and improving the consistency and verifiability of engineering quantity results.

[0179] Example 2:

[0180] refer to Figures 10-25 A BIM-based intelligent quantity calculation system for highways

[0181] I. System Overall Structure and Deployment: The BIM-based intelligent quantity calculation system for highways in this embodiment adopts a combined architecture of "modeling software plug-in / desktop + rule and result server + data storage". The system runs on at least one computing device, which includes a processor, memory, network interface, and readable storage medium; the memory stores program instructions that can be executed by the processor, which are used to implement the functions of each module.

[0182] The system includes: a rule configuration module, a model building and attribute management module, a model verification module, a quantity calculation and bill of quantities generation module, a ledger generation module, and a data storage and interaction module; it can optionally integrate a permission management and log management unit. Each module communicates decoupledly through the interface provided by the data storage and interaction module.

[0183] In one specific deployment method:

[0184] Modeling side: Develop plugins based on the API / SDK of modeling software (such as OpenRoads Designer, MicroStation, Revit, etc.) to be responsible for batch assignment of component attributes, verification and positioning, geometry extraction and write-back;

[0185] Server-side: Provides rule management, computation task scheduling, Boolean operation engine services, templated export services, and incremental update services;

[0186] Data side: Relational databases or document databases are used to centrally store rule bases, mapping bases, verification results, list data, ledger data, and store versions and logs.

[0187] II. Establishment of the Rule Configuration Module and Measurement Rule Base: The rule configuration module is used to configure measurement modeling rules, configure EBS / BOQ / WBS three-structure mapping and matching rules, and establish a component measurement rule base bound to EBS component identifiers. Its typical implementation includes the following sub-units:

[0188] 1. Measurement modeling rule configuration unit, used to constrain the geometric type of components in the target project BIM model (such as solid body, surface, line, parametric family / unit, etc.), and to specify the component information depth (LOD / LOI requirements), quantity calculation attribute fields and WBS attribute fields filling specifications.

[0189] In this embodiment, the system's preset field set includes, for example: Component unique identifier: EID (or GUID); Components Class / Decomposition Identifier: EBS_Code, EBS_Name; Key fields for quantity calculation: QtyType (volume / area / length / quantity, etc.), MeasureUnit, Material, Strength, Spec; WBS fields: WBS_Path (e.g., “Subgrade Engineering / Embankment / … / K12+000~K12+500”) or WBS_KeySet; Analyzable constraints: Geometric closure, normal consistency, unit consistency, etc.

[0190] 2. Three-structure mapping matching rule configuration unit, used to establish the mapping relationship between EBS (Essential Component Breakdown Structure), BOQ (Bill of Quantities Structure), and WBS (Work Breakdown Structure).

[0191] In one implementation, EBS←→BOQ uses a rule matching of "layer name and / or attribute name keywords": maintaining a keyword dictionary (including synonyms, abbreviations, and engineering idioms); segmenting the component's LayerName, FamilyName, TypeName, and custom attribute names; calculating the matching score Score and setting a threshold θ_map, automatically binding to the BOQ sub-item when Score ≥ θ_map.

[0192] Meanwhile, EBS←→WBS←→BOQ achieves three-way association by writing the WBS attribute information of the component, ensuring that the same component can be traced back to the list item and the ledger node.

[0193] 3. The Component Measurement Rule Base Management Unit is used to establish the binding relationship between "EBS Component Identifier - Measurement Rule". Rule entries are identified by RID and include: applicable conditions (component type, material, location, specialty, etc.), measurement scope (gross quantity / net quantity), deduction object type, deduction validity threshold, deduction priority, version number Ver, etc.

[0194] In this embodiment, the rule base supports version freezing: when a calculation task is started, the set of rule versions participating in the calculation is fixed as VerSet for subsequent traceability and consistency updates.

[0195] III. Model Modeling and Attribute Management Module: This module is used to model according to the constraints of quantitative modeling rules and batch assign quantity calculation attributes and WBS attributes, while standardizing component layer names and / or attribute name keywords according to mapping matching rules.

[0196] In this embodiment, the module is implemented as a modeling plugin and provides the following functional flow:

[0197] 1. Component creation constraints: When a user creates or imports a component, the plugin determines in real time whether its geometry type conforms to the quantitative modeling rules. If it does not conform, it will prompt and provide a recommended geometry type on the modeling end (e.g., requiring that solid components cannot be submitted as face-only models).

[0198] 2. Batch assignment of attributes and template inheritance: The plugin loads attribute templates from the rule configuration module and batch writes them into the quantity calculation field and WBS field for the selected range (by line station interval, by profession, by layer, by component type).

[0199] For example, batch writing of roadbed filling components: QtyType=Volume, MeasureUnit=m³, WBS_Path=Roadbed Engineering / Fill / ...

[0200] 3. Keyword standardization assistance: Provides controlled thesaurus selection and automatic error correction for LayerName or key attribute names, reducing mapping failures caused by naming differences; triggers a "keywords to be confirmed" list for words not in the thesaurus, allowing rule personnel to include them in the thesaurus.

[0201] IV. Model Verification Module and Automatic Positioning Reverse Lookup: The model verification module is used to perform creation method verification, quantity calculation attribute verification, and WBS attribute verification, generate a verification list, and drive the modeling software to automatically locate non-compliant components.

[0202] In one specific implementation, the verification module includes at least:

[0203] 1. Verify the creation method, check the geometric closure of components, unit consistency, coordinate system / datum plane consistency, entity validity (e.g., volume > 0), duplicate instances, etc., and output the problem type, problem location, and component EID.

[0204] 2. Quantity calculation attribute verification, verifying field completeness (e.g., if the required field set F_required is missing, it will fail), field value range (strength grade, unit, material enumeration value), and consistency between fields (e.g., volume units must not be written when QtyType=Area).

[0205] 3. WBS attribute verification: Verify the WBS_Path hierarchy depth, keyword parsing capability, and matchability with the project's WBS structure tree; mark components that cannot be matched or have ambiguous matches as "WBS to be assigned".

[0206] 4. Automatic location and reverse lookup: After the checklist is generated, the user clicks on any issue item, and the plugin calls the modeling software API to automatically select and focus the view on the corresponding component, realizing a closed-loop rectification of "issue-component-location".

[0207] V. Quantity Calculation and Bill of Quantities Generation Module (including attribute-geometric association and Boolean operation): The quantity calculation and bill of quantities generation module is used to bind components to BOQ sub-items based on mapping matching rules, and call the component measurement rule library to perform deduction judgment and quantity calculation in combination with Boolean operation; generate and export the bill of quantities according to the preset bill of quantities table style; and write the bill of quantities code, measurement rule identifier and quantity data into the corresponding component as structured attributes.

[0208] Measurement rules are formed based on industry specifications, industry standards, and national standards, and specifically include: calculation formulas and deduction rules; further, it should be understood that users can modify and customize recording rules for each component, including agreeing on the calculation formulas and deduction rules for the component's quantity of work.

[0209] 1) Attribute-Geometric Association Unit: This unit interfaces with the modeling software API to extract component attribute data and establish a one-to-one mapping with the 3D geometric model. In this embodiment, the component's unique identifier EID is used as the index key to form a record: EID → {GeometryRef, BoundingBox, AttributeSet}; and the geometric reference is cached in memory or a geometric cache library to support subsequent spatial indexing and Boolean operations for acceleration.

[0210] 2) The rule-bound deduction calculation engine uses EID as an index to call the bound metering rule base entries (RID, Ver), and determines the validity of the geometric interaction of intersecting components based on rule parameter thresholds. Its typical processing flow is as follows:

[0211] 1. Candidate intersection retrieval: First, establish a spatial index based on bounding boxes (such as AABB tree / grid index) to quickly filter the set of potentially intersecting components, Cands (EID).

[0212] 2. Validity determination: For each candidate deduction component EIDj, calculate the degree of intersection index, such as the overlap volume ratio. It also combines threshold θ_r, contact depth threshold θ_d, component type constraints, etc., to determine whether it is a "valid deduction".

[0213] 3. Boolean intersection / difference operation and net quantity calculation: When the validity judgment is met, perform Boolean intersection operation to obtain the intersection set and calculate the intersection quantity; when the rule application conditions are met, perform Boolean difference operation on the deducted component to obtain the net geometric quantity after deduction.

[0214] When the same deducted component corresponds to multiple deducted components, the components are deducted sequentially according to the deduction priority Pr in the rule entry and the deduction is updated cumulatively to avoid duplicate deductions or missed deductions.

[0215] 4. Output gross / net quantities, output gross quantity Q_gross and net quantity Q_net, and retain the deduction details list (deduction object, intersection quantity, priority, rule version, etc.).

[0216] 3) The BOQ information write-back unit writes the BOQ sub-item code, the adopted measurement rule number RID and rule version number Ver, the gross quantity before deduction, the net quantity after deduction, and the deduction traceability information of the component into the structured attribute field of the corresponding BIM component, forming a one-to-one association link of "component - rule - BOQ - quantity".

[0217] In one implementation, the write-back fields are as follows: BOQ_Code, BOQ_Name, RID, Ver; Qty_Gross, Qty_Net, Deduct_Trace (in JSON / key-value pair format, recording the deduction sequence and its intersection).

[0218] 4) Templated generation and export of bill of quantities: The system generates a bill of quantities according to a preset table style (field order, unit format, summary scope, and professional category), and supports exporting to Excel, XML, or other formats recognizable by cost estimation software. The exported data includes the VerSet of this task and a generation timestamp, ensuring traceability.

[0219] VI. The No. 0 ledger generation module is consistent with the incremental update. The No. 0 ledger generation module is used to automatically match the WBS attributes of the components with the WBS hierarchical structure of the No. 0 ledger based on the WBS keyword matching algorithm, and automatically fill in the No. 0 ledger according to the ledger format to generate and export the No. 0 ledger.

[0220] 1) WBS Keyword Matching Algorithm: In this embodiment, the WBS_Path or WBS_KeySet of the component is standardized and segmented to obtain the keyword set Kc; the keyword set Kn and hierarchical path are maintained for each node of the ledger WBS tree. The system calculates the similarity Sim(Kc,Kn) and selects the node with the maximum similarity as the matching node; when the maximum similarity is lower than the threshold θ_wbs, "node to be confirmed" is output for manual correction once and then settled into the mapping rule.

[0221] 2) The ledger is automatically filled. After the matching is completed, the system summarizes the component quantities (usually Qty_Net) under the same WBS node according to the ledger format, based on dimensions such as BOQ sub-item and unit of measurement, and outputs ledger number 0.

[0222] 3) The incremental update mechanism is consistent with the rule version. The No. 0 ledger generation module establishes a mapping relationship between "component unique identifier - ledger WBS node" based on the structured attribute fields and WBS attributes, and only performs incremental updates on the affected WBS nodes when the component quantity or list information changes.

[0223] In one implementation, the system maintains a fingerprint for each component:

[0224] When the hash changes, the component is marked as "dirty data," and only its associated BOQ rows and WBS nodes are recalculated, avoiding a full recalculation. The ledger output also carries a rule version traceability field (such as VerSet_ID), thereby achieving consistent generation and updating of the bill of quantities and ledger No. 0 under the same rule version.

[0225] VII. Data Storage and Interaction Module, Permissions and Logs: The data storage and interaction module is used to centrally store rule data, model data, verification results, list data and ledger data, and provides data interaction interfaces between modules.

[0226] In this embodiment, the data storage and interaction module includes at least:

[0227] Rule base tables / sets: RuleSet(RID,Ver,Cond,Params,Priority,...), MappingRule(...);

[0228] Model index table / set: Component(EID, GeomRef, Attrs, ...), SpatialIndex(...);

[0229] Check result table / set: CheckIssue(EID,Type,Desc,Severity,...);

[0230] Lists and ledgers / collections: BOQLine(BOQ_Code,Qty,Unit,...), LedgerNode(WBS_Node,QtySum,...);

[0231] Furthermore, the data storage and interaction module includes access control and log management units:

[0232] Access control is configured, verified, and quantity calculation operation permissions are controlled by role-based rules (e.g., rule administrators, modelers, verifiers, and cost estimators are read-only).

[0233] Log management records operation logs for rule creation, model modification, quantity calculation execution, and result export. Log entries must include at least the operator, time, object identifier (EID / RID / Ver), operation type, and difference summary to facilitate audit traceability.

[0234] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A BIM-based intelligent quantity calculation method for highways, characterized in that, The specific steps include the following: S01 creates a highway engineering measurement modeling rule to constrain the geometric type of components in the target project BIM model, and specifies the filling specifications for component information depth, quantity calculation attribute fields and WBS attribute fields, so that the geometry and attributes of the components can be parsed to generate engineering quantities and can be matched with the engineering quantity list sub-item feature items and the 0th ledger WBS structure tree. S02 creates mapping and matching rules for the three components of the BIM model: Component Decomposition Structure (EBS), Bill of Quantities (BOQ), and Project Component Structure (WBS). The mapping and matching rules include at least: automatic mapping and association between EBS and BOQ based on text keywords of component layer names and / or attribute names, and three-way association between components in EBS, BOQ, and WBS based on the WBS attribute information written to the components. S03 Establish a component measurement rule library, convert industry measurement rules into structured machine-readable rules and bind them to EBS component identifiers, and call the rule library during quantity calculation. Through Boolean operations, perform deduction judgment and deduction calculation in accordance with industry measurement rules for components with spatial intersection relationships. S04 performs BIM modeling of the target project according to the measurement modeling rules and assigns quantity calculation attributes and WBS attributes to the components, and standardizes the layer name, attribute name and text keywords of the components according to the mapping matching rules. S05 performs creation method verification, quantity calculation attribute verification, and WBS attribute verification on the target project BIM model. For components that fail the verification, a verification list is generated and the spatial location and attribute information of the corresponding components are automatically located in the modeling software. After the verification is passed, S06 sets the bill of quantities table style, binds the components to the BOQ sub-items based on the mapping and matching rules of EBS and BOQ, calculates the component quantities according to the component measurement rule library, and outputs the bill of quantities according to the table style. S07 embeds the corresponding list code, measurement rule identifier, and calculated quantity data of the component into the corresponding component of the BIM model in the form of structured attributes; S08 presets the standard format of Ledger No. 0, extracts the WBS attributes of the components and the embedded list information and quantity data, and automatically matches the component WBS attributes with the WBS hierarchical structure of Ledger No. 0 based on the WBS keyword matching algorithm and establishes a mapping relationship. It then automatically fills in and exports the results of Ledger No. 0 according to the ledger format.

2. The intelligent quantity calculation method for highways based on BIM according to claim 1, characterized in that, The component measurement rule base uses the EBS decomposition structure as the rule index framework and establishes rule entries for each EBS component's unique identifier EID. The rule entry shall include at least: rule number RID, rule version number Ver, effective time Te, applicable condition set Cond, parameter set Param, deduction priority Pr, and applicable metering object type identifier Type; The parameter set Param includes at least: geometric calculation accuracy threshold ε, hole deduction threshold D0, and mapping score threshold τ; The rule base sets traceability field constraints, requiring that at least each quantity calculation output is associated with the record RID, Ver, and Te, and can be traced back to the corresponding EID and the set of component identifiers involved in the deduction; The dynamic update mechanism includes: performing a difference comparison on rule entries with the same RID but different Ver to determine the scope to be updated; batch binding the updated Cond and Param to the corresponding EID; retaining at least the previous version of the rule for traceability, and recording the rule update time, updater identifier, and modification log.

3. The intelligent quantity calculation method for highways based on BIM according to claim 1, characterized in that, The process of performing deduction determination and deduction calculation through Boolean operations includes: performing Boolean intersection operations on intersecting components to obtain geometric intersection sets and calculating the intersection quantity, wherein the intersection quantity is determined based on the measurement object according to volume, area or length; Set a geometric calculation accuracy threshold ε. When the intersection amount is not greater than ε, it is judged as an invalid intersection and no deduction is performed. When the intersection is greater than ε, the deduction rule bound to the EID of the deducted component is invoked, and the key parameters of the deducted component are verified according to the applicable condition set Cond. If the verification passes, Boolean difference operation is performed and deduction is performed according to the difference set. If the verification fails, the original quantity of the project is maintained. When the same deducted component intersects with multiple deducted components at the same time, the components are deducted in descending order of deduction priority Pr, and the intermediate results after each deduction are cumulatively updated. The deduction process records traceability information, including at least: the identifier of the deducted component, the identifier of the deducted component, the intersection quantity, the RID and Ver used, the determination result of whether the deduction is effective, and the net quantity result after deduction.

4. The intelligent quantity calculation method for highways based on BIM according to claim 1, characterized in that, The industry measurement rules include a hole deduction threshold rule, and define the hole equivalent size parameter D and the threshold D0; When D is not greater than D0, the hole is not included in the deduction of the project quantity; When D is greater than D0, the hole is deducted according to the amount of intersection formed between it and the component being deducted. The equivalent size parameter D of the hole is calculated from the geometric parameters of the hole, and the geometric parameters include at least one of the hole diameter, the short side of the hole, the long side of the hole, or the cross-sectional area of ​​the hole. The threshold D0 is written into Param as a configurable parameter of the rule base and can be set with different values ​​according to the component type Type. The hole deduction result is written into the traceability field, which includes at least the hole component identifier, D value, D0 value, whether deduction is performed, and the RID and Ver used.

5. The intelligent quantity calculation method for highways based on BIM according to claim 1, characterized in that, The mapping matching rules include a keyword dictionary Dict, a matching weight parameter W, a matching score threshold τ, a matching priority Level, a mutual exclusion table Mutex, and an exception list ExList; Extract keyword sets from the layer names and / or attribute names of components, and match and score them with the feature item keyword sets of candidate BOQ sub-items. The scoring results are used to determine whether to establish a mapping association between EBS and BOQ. When the score of a candidate BOQ sub-item is not less than the threshold τ, a mapping association is established. When multiple candidate BOQ sub-items meet the threshold at the same time, a unique mapping result is determined according to the priority level. Set a unique attachment constraint: Except for component types belonging to the exception list ExList, the same component is only allowed to attach one BOQ sub-item code and one WBS node code at the same time; Set up a conflict handling mechanism: When the same component is mapped to multiple BOQ sub-items or multiple mutually exclusive WBS nodes defined in the Mutex table, output a conflict record and mark the component as "to be reviewed" to block automatic summary output; The conflict record must include at least the following fields: unique component identifier, candidate target list, respective score, priority, mutual exclusion basis, trigger time, and processing status, to meet the requirements of verifiability and traceability.

6. The intelligent quantity calculation method for highways based on BIM according to claim 1, characterized in that, The model verification includes at least the verification of the creation method, the verification of the computational quantity attribute, and the verification of the WBS attribute; The verification of the creation method includes at least: whether the component geometry type conforms to the metrological modeling rules, whether the component has abnormal geometry such as non-closed body or self-intersection, and whether the component meets the minimum measurable scale threshold. The verification of the quantity calculation attributes includes at least: whether the required quantity calculation fields are complete, whether the field types and value ranges meet the preset constraints, whether the unit of measurement is consistent with the unit of the list item, and whether the key threshold parameters are correctly inherited or filled in. The WBS attribute verification includes at least: whether the WBS code exists, whether the coding level meets the layer depth constraint parameter H, whether the code and component type meet the consistency constraint, and whether the unique attachment constraint is met. Output a checklist and support automatic location of failed components in the modeling software. The checklist shall include at least the component's unique identifier, problem type, spatial coordinates, missing or abnormal field name, current field value, and reference to the suggested repair rule entries. The traceability fields for the verification and repair process records should include at least the attribute differences before and after repair, the repairer's identifier, and the repair time.

7. The intelligent quantity calculation method for highways based on BIM according to claim 1, characterized in that, The bill of quantities table style shall at least limit the set of fields, the order of fields, the constraints of field format and the consistency of measurement units; While outputting the bill of quantities, a reverse association index is established so that the corresponding set of components can be retrieved for any item code and item name in the bill of quantities. The component records of the reverse association index include at least: a unique component identifier, a bill of quantities item code, a bill of quantities item name, an identification number of the measurement rule used (RID), a rule version number (Ver), a summary of key parameters, and the calculated quantity of the bill of quantities. Set a unique attachment constraint verification: For non-exceptional list ExList components, if multiple list item codes are detected for the same component, an attachment exception record will be output and the component will be blocked from participating in the list summary. When a discrepancy is detected between the unit of measurement of a component and the unit of measurement of a sub-item in the bill of quantities, the unit is converted according to the preset unit conversion table or an inconsistency alarm is output and the automatic summarization of that sub-item is blocked. Each sub-item summary row of the bill of quantities shall record traceability fields, including at least the number of components involved in the summary, the component identifier list reference, the rule version information used, and the generation timestamp.

8. The intelligent quantity calculation method for highways based on BIM according to claim 1, characterized in that, The automatic generation of Ledger 0 includes establishing a mapping relationship Map of "component unique identifier - ledger WBS node", and automatically summarizing and filling the component engineering quantity under the same WBS node according to the mapping relationship; The No. 0 ledger adopts a preset standard format, which includes at least WBS level fields, list item fields, unit of measurement fields, quantity fields, and source traceability fields. The source tracing fields include at least: associated component set reference, list item code, rule number RID, rule version number Ver, mapping rule version identifier and generation timestamp; The linked update includes an incremental update mechanism: when the quantity or bill of quantities information of any component changes, only the ledger record corresponding to the WBS node to which the component belongs is updated incrementally, and the "update time identifier" and source traceability field are updated simultaneously. When the component mapping relationship changes, first perform mapping change verification and output a change list. The change list should include at least the changed component identifier, the original WBS node, the new WBS node, the reason for the change, and the effective time. Then, recalculate or incrementally correct the affected WBS nodes. The process of exporting ledgers should record export traceability information, including at least the export format, export file identifier, exporter identifier, and export time.

9. A BIM-based intelligent quantity calculation system for highways, characterized in that, include: The rule configuration module is used to configure metrological modeling rules, configure EBS / BOQ / WBS three-structure mapping and matching rules, and establish a component metrological rule library bound to EBS component identifiers; The modeling and attribute management module is used to constrain modeling according to quantitative modeling rules and batch assign quantity calculation attributes and WBS attributes, while standardizing component layer names and / or attribute name keywords according to mapping matching rules. The model verification module is used to perform verification of creation method, quantity calculation attribute and WBS attribute, generate verification list and drive the modeling software to automatically locate non-compliant components; The quantity calculation and bill of quantities generation module is used to bind components to BOQ sub-items based on mapping matching rules, and call the component measurement rule library to perform deduction judgment and quantity calculation in combination with Boolean operation. It generates and exports the bill of quantities according to the preset bill of quantities table style, and writes the bill of quantities code, measurement rule identifier and quantity data into the corresponding component as structured attributes. The No. 0 ledger generation module is used to automatically match the WBS attributes of components with the WBS hierarchical structure of No. 0 ledger based on the WBS keyword matching algorithm, automatically fill in the ledger format to generate No. 0 ledger, and then export it. The data storage and interaction module is used to centrally store rule data, model data, verification results, list data, and ledger data, and provides data interaction interfaces between modules.

10. The BIM-based intelligent quantity calculation system for highways according to claim 9, characterized in that, The quantity calculation and bill of quantities generation module includes a rule-bound deduction calculation engine and a bill of quantities information write-back unit, wherein: The deduction calculation engine bound to the rule is used to call the component measurement rule library entries bound to it using the unique identifier EID of the EBS component as an index, and to determine the validity of the geometric interaction of intersecting components based on the rule parameter threshold; when the validity determination is met, a Boolean intersection operation is performed on the intersecting components to obtain the intersection set and the intersection quantity is calculated, and a Boolean difference operation is performed on the deducted component to obtain the net quantity after deduction when the rule application conditions are met; when the same deducted component corresponds to multiple deducted components, the deductions are performed sequentially according to the deduction priority in the rule entry and the cumulative update is performed; The measurement rules are formed in accordance with relevant specifications and standards, and include: calculation formulas and deduction rules; The list information write-back unit is used to write the list item code, list item name, adopted measurement rule number RID and rule version number Ver, quantity before deduction, net quantity after deduction, and deduction traceability information of the component to the structured attribute fields of the corresponding BIM component. The No. 0 ledger generation module establishes a mapping relationship between "component unique identifier - ledger WBS node" based on the structured attribute fields and WBS attributes. When the component quantity or list information changes, it only performs incremental updates on the affected WBS nodes and outputs a traceability field containing rule version information.

Images