Information management method and system for engineering cost

Abstract

The application relates to the field of engineering cost information processing, and discloses an information management method and system for engineering cost; the method acquires bill of quantities data, contract data, design change data, field visa data, progress confirmation data, settlement data, price information data and pricing rule data, and carries out standardized processing to form a cost event unit; an event fingerprint is generated based on the cost event unit to identify homologous relationship, repeated relationship, covering relationship and conflict relationship; a cost influence graph is constructed to determine corresponding price version nodes and pricing rule version nodes; when the cost event unit is newly added, changed or withdrawn, an event subgraph is extracted to execute local propagation recalculation, a stage cost snapshot and an evidence chain result package are generated, and the application can improve the accuracy, traceability and auditing efficiency of engineering cost processing.

Description

Technical Field

[0001] This invention relates to the field of engineering cost information processing, and specifically to information management methods and systems for engineering cost. Background Technology

[0002] During the implementation of engineering construction projects, various cost-related data are typically generated, including bill of quantities, contract terms, design changes, site instructions, progress confirmations, and settlement audits. These data correspond to different business stages and collectively affect the measurement, adjustment, and phased settlement of project costs. Therefore, it is necessary to manage and continuously account for multi-source cost information in a unified manner.

[0003] Existing engineering cost information management methods mostly involve filing documents separately according to document type, or entering, circulating, summarizing and querying design changes, site visas, progress confirmations and settlement data according to the approval process. Some schemes also combine bill of quantities, price documents or model data to perform difference statistics in order to form cost reports, audit basis or settlement basis data.

[0004] However, due to the differences in the names of engineering objects, scope of application, measurement standards, confirmation time and pricing basis of documents from different sources, the same cost item may be repeatedly recorded or cross-referenced in multiple stages. Furthermore, subsequent changes, visas and settlement adjustments will continue to change the original correspondence, thereby gradually destabilizing the cost impact boundary. This makes it difficult for the existing scheme to identify the true impact range of the same item in a timely and accurate manner, which can easily lead to problems such as double pricing, omissions and inconsistent application of rules, affecting the accuracy of cost results and audit efficiency. Summary of the Invention

[0005] In view of the shortcomings of the prior art, the present invention provides an information management method and system for engineering cost, so as to solve the technical problems existing in the prior art.

[0006] The above-mentioned technical objective of the present invention is achieved through the following technical solution: Information management methods and systems for engineering cost include the following steps: S1: Obtain the bill of quantities data, contract data, design change data, site visa data, progress confirmation data, settlement data, price information data, and pricing rule data corresponding to the target project, and standardize the obtained data according to the unified field specification to form multiple cost event units. Each cost event unit includes the project object identifier, bill of quantities item identifier, contract section identifier, scope identifier, quantity change characteristics, pricing basis identifier, occurrence time, approval status, and source document identifier. S2: Based on the engineering object identifier, list item identifier, contract section identifier, scope identifier, quantity change characteristics, occurrence time, approval status and source document identifier of each cost event unit, generate the corresponding event fingerprint according to the preset combination rules, and identify the same source relationship, duplicate relationship, coverage relationship and conflict relationship between cost event units according to the event fingerprint and the preset matching rules. S3: Based on the correspondence between each cost event unit and the bill of quantities, as well as the identified common source relationship, duplicate relationship, coverage relationship and conflict relationship, construct the cost impact map. The cost impact map includes bill of quantities item nodes, engineering object nodes, cost event nodes, price version nodes, pricing rule version nodes and settlement nodes, as well as source relationship edges, substitution relationship edges, supplementary relationship edges, exclusion relationship edges and amount impact relationship edges connecting each node; S4: For each cost event unit, based on its occurrence time, approval status, contract clause effectiveness information, contract segment to which it belongs and corresponding list item category, determine the corresponding price version node and pricing rule version node from the price information data and pricing rule data, and write the determination results into the cost impact map. S5: When any cost event unit is added, changed, or withdrawn, the corresponding cost event node is taken as the starting node, the event subgraph associated with the starting node is extracted, and local propagation recalculation is performed along the substitution relationship edge, supplementary relationship edge, exclusion relationship edge and amount influence relationship edge in the event subgraph to determine the scope of affected list items, quantity difference, applicable price version, measure fee adjustment result and tax adjustment result, and generate the corresponding stage cost snapshot; S6: Based on the identification results of duplicate relationships, coverage relationships, and conflict relationships, as well as the local propagation recalculation results and the phased cost snapshot, output the corresponding items to be audited, duplicate pricing doubts, omission doubts, and rule application doubts, and simultaneously generate an evidence chain result package for each item to be audited. The evidence chain result package includes at least the source file identifier field, event fingerprint field, version application field, propagation path field, conflict determination field, and amount difference field.

[0007] Preferably, the standardization process of the acquired data according to a unified field specification specifically includes: Extract the following information from contract data, design change data, site visa data, progress confirmation data, and settlement data: project object identification information, list item identification information, contract section identification information, scope identification information, quantity change characteristics, occurrence time information, approval status information, and source document identification information. According to the preset mapping rules, fields with different names in different data sources are converted into unified field names and written to the corresponding cost event units; For data items that cannot be directly mapped to the bill of quantities, an association mapping relationship between them and the target bill of quantities items is established based on the project object identifier, scope identifier, and contract section identifier.

[0008] Preferably, the identification of homology, duplication, overlap, and conflict relationships among cost event units based on the event fingerprint and preset matching rules specifically includes: When two cost event units have the same project object identifier, list item identifier, contract section identifier, and scope identifier, their occurrence time is within a preset time window, and their corresponding source file types belong to a preset associated file combination, it is determined that the two have a common source relationship. When two cost event units have a common origin and consistent quantity change characteristics, it is determined that the two have a duplicate relationship; When two cost event units correspond to the same item in the bill of quantities, and the scope of one cost event unit covers the scope of the other cost event unit, it is determined that there is an overlap relationship between the two. When two cost event units correspond to the same item in the bill of quantities, and they result in inconsistent pricing basis or inconsistent quantity changes, it is determined that there is a conflict between them.

[0009] Preferably, the conflict relationships include overlay conflicts, duplication conflicts, rule conflicts, and time conflicts; For cost event nodes that have overlapping conflicts, the low-priority amount impact relationship edge corresponding to the covered cost event node is temporarily blocked. For cost event nodes with duplicate conflicts, the edges corresponding to the duplicate amount impact relationships in the duplicate cost event nodes are temporarily masked. For cost event nodes with rule conflicts or time conflicts, the corresponding monetary impact edges will not participate in local propagation recalculation until the conflict determination is completed.

[0010] Preferably, determining the corresponding price version node and pricing rule version node based on its occurrence time, approval status, contract clause effectiveness information, contract segment, and corresponding list item category specifically includes: Candidate price versions are determined based on the occurrence time of cost event units; The candidate pricing rule version is determined based on the approval status and contract terms effectiveness information; Based on the contract section and corresponding list item category, filter the target price version and target pricing rule version from the candidate price version and candidate pricing rule version; When the target price version or target pricing rule version is switched, only the event subgraph associated with the cost event unit is recalculated locally.

[0011] Preferably, extracting the event subgraph associated with the starting node specifically includes: Using the starting node as the center node, extract the associated nodes and associated edges that are connected to the starting node and whose path length does not exceed a preset level threshold; The extracted associated nodes and edges are used to construct an event subgraph for local propagation recalculation. The phased cost snapshot records at least the set of affected list items, the set of related cost events, the applicable price version, the applicable pricing rule version, the difference in quantities, the adjustment results of the measures fee, and the adjustment results of taxes at the corresponding time.

[0012] An information management system for engineering cost estimation includes: Includes memory, processor, and computer programs stored in memory and capable of running on the processor; When the processor executes the computer program, it is also used to: The acquired contract data, design change data, site visa data, progress confirmation data, and settlement data are processed to extract field information, including project object identification information, list item identification information, contract section identification information, scope identification information, quantity change characteristics information, occurrence time information, approval status information, and source document identification information. Convert fields with different names from different data sources to a unified field name according to the preset mapping rules; Establish a mapping relationship between the project object identifier, scope identifier, and contract section identifier and the target list items.

[0013] Preferably, when the processor executes the computer program, it is further configured to: The event fingerprint is generated by combining the project object identifier, list item identifier, contract section identifier, scope identifier, quantity change characteristics, occurrence time, approval status, and source document identifier according to the preset combination rules. Based on the event fingerprint, the homology, duplication, overlay and conflict relationships between cost event units are identified. Based on the identified homologous, duplicate, overlapping, and conflicting relationships, the corresponding monetary impact edges in the cost impact map are either masked or restored.

[0014] Preferably, when the processor executes the computer program, it is further configured to: When any cost event unit is added, changed, or withdrawn, the event subgraph associated with the corresponding cost event node is extracted; Local propagation recalculation is performed within the event subgraph along the substitution, supplementary, exclusionary, and monetary influence edges. Generate an evidence chain result package that includes source file identifier field, event fingerprint field, version applicable field, propagation path field, conflict determination field, and amount difference field.

[0015] In summary, the present invention has the following main beneficial effects: This application unifies the data from bill of quantities, contracts, design changes, site approvals, progress confirmations, settlements, pricing information, and pricing rules into a unified cost event unit. Each cost event unit is assigned an identifier for the project object, bill of quantities item, contract section, scope of application, quantity change characteristics, pricing basis, occurrence time, approval status, and source document. By transforming cost-related information scattered across different business documents into a unified, comparable, and traceable data object, this application reduces identification biases caused by inconsistencies in document names, terminology, and record granularity. This allows for accurate extraction and continuous tracking of the same cost item within a unified field system. Furthermore, by generating event fingerprints based on cost event units and identifying relationships of origin, duplication, overlap, and conflict, the application further reduces the risks of duplicate pricing, omissions, and errors, improving the accuracy of cost data processing and item merging.

[0016] By constructing a cost impact graph that includes list item nodes, engineering object nodes, cost event nodes, price version nodes, pricing rule version nodes, and settlement nodes, and upon detecting the addition, modification, or withdrawal of a cost event unit, the event subgraph associated with the starting node is extracted. Local propagation recalculation is then performed within this event subgraph along substitution, supplementary, exclusionary, and monetary impact edges. This transforms the cost processing from traditional whole-table comparison, manual backtracking, and global duplicate accounting into local propagation calculation oriented towards the affected scope. This achieves the effect of clarifying the scope of affected list items, quantity differences, applicable price versions, adjustment results for provisional costs, and tax adjustment results, while simultaneously narrowing the recalculation scope, improving recalculation efficiency, and establishing a stable correspondence between the cost change process and its results. Especially in scenarios where design changes, site approvals, measurement confirmations, and settlement audits overlap, this effectively avoids the problem of duplicate accounting for the entire project caused by changes in local matters.

[0017] By identifying duplicate, overlapping, and conflicting relationships, along with local propagation recalculation results and interim cost snapshots, the system outputs items to be audited, suspected duplicate pricing, suspected omissions, and suspected rule application issues. Simultaneously, it generates an evidence chain result package including source document identifier fields, event fingerprint fields, version application fields, propagation path fields, conflict determination fields, and amount difference fields. By integrating cost difference results with source document origins, relationship identification results, version adaptation results, and amount formation paths, the system enables auditors to directly trace which business documents triggered a specific amount difference, through what relationships it propagated, and which price and pricing rule versions were applied. This improves the interpretability, verifiability, and processing efficiency of cost audits, process reviews, and settlement dispute resolution. Attached Figure Description

[0018] Figure 1 This is a flowchart of the method of the present invention. Detailed Implementation

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

[0020] Example 1 refer to Figure 1 An information management method for engineering cost includes the following steps: S1: Obtain the bill of quantities data, contract data, design change data, site visa data, progress confirmation data, settlement data, price information data, and pricing rule data corresponding to the target project, and standardize the obtained data according to the unified field specification to form multiple cost event units. Each cost event unit includes the project object identifier, bill of quantities item identifier, contract section identifier, scope identifier, quantity change characteristics, pricing basis identifier, occurrence time, approval status, and source document identifier. S2: Based on the engineering object identifier, list item identifier, contract section identifier, scope identifier, quantity change characteristics, occurrence time, approval status and source document identifier of each cost event unit, generate the corresponding event fingerprint according to the preset combination rules, and identify the same source relationship, duplicate relationship, coverage relationship and conflict relationship between cost event units according to the event fingerprint and the preset matching rules. S3: Based on the correspondence between each cost event unit and the bill of quantities, as well as the identified common source relationship, duplicate relationship, coverage relationship and conflict relationship, construct the cost impact map. The cost impact map includes bill of quantities item nodes, engineering object nodes, cost event nodes, price version nodes, pricing rule version nodes and settlement nodes, as well as source relationship edges, substitution relationship edges, supplementary relationship edges, exclusion relationship edges and amount impact relationship edges connecting each node; S4: For each cost event unit, based on its occurrence time, approval status, contract clause effectiveness information, contract segment to which it belongs and corresponding list item category, determine the corresponding price version node and pricing rule version node from the price information data and pricing rule data, and write the determination results into the cost impact map. S5: When any cost event unit is added, changed, or withdrawn, the corresponding cost event node is taken as the starting node, the event subgraph associated with the starting node is extracted, and local propagation recalculation is performed along the substitution relationship edge, supplementary relationship edge, exclusion relationship edge and amount influence relationship edge in the event subgraph to determine the scope of affected list items, quantity difference, applicable price version, measure fee adjustment result and tax adjustment result, and generate the corresponding stage cost snapshot; S6: Based on the identification results of duplicate relationships, coverage relationships, and conflict relationships, as well as the local propagation recalculation results and the phased cost snapshot, output the corresponding items to be audited, duplicate pricing doubts, omission doubts, and rule application doubts, and simultaneously generate an evidence chain result package for each item to be audited. The evidence chain result package includes at least the source file identifier field, event fingerprint field, version application field, propagation path field, conflict determination field, and amount difference field.

[0021] The information management system for engineering cost estimation includes a memory, a processor, a communication interface, and a computer program stored in the memory. When the processor executes the computer program, it implements the aforementioned method.

[0022] At the program implementation level, the computer program may include a data access processing program, a field standardization processing program, an event fingerprint generation program, a relationship identification program, a cost impact graph construction program, a version adaptation program, a conflict edge control program, an event subgraph extraction program, a local propagation recalculation program, a phased cost snapshot generation program, and an evidence chain result package generation program.

[0023] The input / output relationships between the programs are as follows: The data access processing program outputs raw business data; The field standardization processing program takes raw business data as input and outputs a set of standardized fields; The event fingerprint generation program takes a standardized set of fields as input and outputs cost event units and event fingerprints. The relationship identification program takes cost event units and event fingerprints as inputs and outputs homology relationships, duplicate relationships, overriding relationships, and conflict relationships. The cost impact map construction program takes cost event units, relationship identification results, price information data and pricing rule data as inputs, and outputs a cost impact map. The version adaptation program takes cost event units, contract terms information, and price information data as input, and outputs price version nodes and pricing rule version nodes. The conflict edge control procedure takes the conflict relationship identification result as input and outputs the participation status of the relationship edge by the amount of money involved. The event subgraph extraction program takes the initial cost event node and the cost impact map as input and outputs an event subgraph. The local propagation recalculation procedure takes the event subgraph, the participation status of the monetary impact relationship edge, the price version node, and the pricing rule version node as inputs, and outputs the quantity difference, monetary difference, adjustment result of the measure fee, and adjustment result of the tax. The phased cost snapshot generation program and the evidence chain result package generation program take the local propagation recalculation results as input and output the phased cost snapshot and the evidence chain result package, respectively.

[0024] In this embodiment, the data sources accessed by the system include bill of quantities data, contract data, design change data, site approval data, progress confirmation data, settlement data, price information data, and pricing rule data.

[0025] Specifically, the bill of quantities data can be derived from the tender list, contract list, supplementary list, or internal list after review and confirmation; contract data can be derived from the construction contract, professional subcontracting contract, supplementary agreement, and contract price adjustment clause; design change data can be derived from design change notices, design liaison forms, and detailed design confirmation forms; site visa data can be derived from site visa forms, engineering liaison forms, and engineering negotiation records; progress confirmation data can be derived from monthly bill of quantities confirmation forms, measurement payment application forms, or physical progress confirmation forms; settlement data can be derived from the settlement draft, sub-item settlement statements, and final settlement submission documents; price information data can be derived from the price information documents adopted in the contract, price documents issued by the engineering cost management agency, and confirmed material and equipment pricing documents; and pricing rule data can be derived from the pricing method, applicable quotas, fee rules, and tax rate rules agreed upon in the contract.

[0026] To avoid ambiguity caused by using different names for the same content in different documents, this embodiment sets a unified field specification and maps all input data to the unified field specification. The unified field specification includes at least the project object identifier, list item identifier, contract section identifier, scope identifier, quantity change characteristics, pricing basis identifier, occurrence time, approval status, and source document identifier.

[0027] The unified field specifications are pre-stored in the field mapping rule base. The field mapping rule base is established during the project initialization phase, based on the target project's list coding system, contract numbering system, engineering breakdown structure coding system, floor or section coding system, and document numbering rules. The field mapping rule base is not generated temporarily during runtime, but rather formed when the system integrates the first batch of project data, and is only updated subsequently when new coding types are added.

[0028] in: The project object identifier is used to uniquely represent the project object corresponding to the cost impact, and is preferably formed by a combination of project breakdown structure code, professional code and spatial location code; The item identifier is used to uniquely identify a measurable and priced item in the list. It can be a tender list code, a supplementary list code, or an internal mapping code that has been reviewed and confirmed. Contract section identifiers are used to distinguish different bid sections, different contract packages, or different boundaries of responsibility; The scope of effect identifier is used to characterize the spatial range, location range, or work scope in which the cost impact occurs; The quantitative change characteristics include at least the change type and the change value. The change type includes addition, reduction, replacement, cancellation, splitting and merging. The pricing basis identifier is used to identify the source of the pricing basis corresponding to this cost event; The occurrence time is used to characterize the time when the cost event is confirmed to have entered the cost processing flow; The approval status is used to indicate whether the cost event meets the conditions for participating in the propagation calculation; The source file identifier is used to uniquely identify the original file source that forms the cost event unit.

[0029] In this embodiment, each original business document is parsed to form at least one cost event unit; when an original business document involves multiple engineering objects, multiple list items or multiple different scopes, the system splits it into multiple cost event units according to the engineering object identifier, list item identifier and scope identifier.

[0030] For example, if a design change notice includes both structural reinforcement and mechanical and electrical pipeline adjustments, the system will generate separate cost event units for each; if a site approval form covers different floors and different bill of quantities items, the system will split it according to the floors and bill of quantities items.

[0031] The process of forming a cost event unit includes the following steps: The first step is field extraction. The system extracts information from the original file, including project name, contract number, document number, engineering location, construction method description, engineering quantity description, pricing caliber description, issuance time, confirmation time, and approval conclusion. Extraction methods can include structured form reading, template parsing, rule matching, or manual data entry and verification.

[0032] The second step is field merging. For cases where different descriptions exist for the same project object, the system merges them according to the field mapping rule base to form a unified project object identifier. For cases where the tender list code and internal calculation code are inconsistent for the same list item, the system forms a unified list item identifier based on the list mapping table.

[0033] The third step is cost impact breakdown. For entries in the same file that contain both increases and decreases, the system splits them into two cost event units. For entries that only change the method but do not directly provide changes in the quantity, the system retains the pricing basis identifier and the scope identifier, and sets the quantity change characteristic to a pending completion status, to be completed after being associated with progress confirmation data or measurement and payment data.

[0034] To ensure the clarity and unambiguity of the sources of the preset rules, thresholds, and coefficients in the specification, this embodiment establishes the following rule base during the project initialization phase and calls it during runtime: Firstly, the field mapping rule library is used to merge heteronymous fields and form unified fields. Its source is the target project's list coding system, contract numbering system, project breakdown structure coding system, and document numbering rules.

[0035] Secondly, a document type association rule base is used to determine preset associated document combinations, which are derived from project management and contract management processes. For example, a design change notice and a site work order form constitute a preset associated document combination; a site work order form and a monthly quantity confirmation form constitute a preset associated document combination; and a progress confirmation form and a draft settlement form constitute a preset associated document combination. These preset associated document combinations are not arbitrarily specified, but rather established based on document types that are sequentially connected, mutually referenced, or mutually verified in actual business operations.

[0036] Third, the business cycle rule base is used to determine the preset time window, which is derived from the project's agreed measurement and payment cycle, change approval cycle, and settlement review cycle.

[0037] Fourth, the measurement accuracy rule base is used to determine the allowable error range. Its sources are the measurement units agreed upon in the contract, the rules for retaining decimal places, the conversion rules, and the audit rounding rules.

[0038] Fifth, the approval participation rule base is used to determine whether each approval status participates in the local propagation recalculation. Its source is the project approval flow definition and contract management requirements.

[0039] Sixth, the conflict edge control rule base is used to determine the low-priority monetary impact relationship edges and their shielding conditions. Its sources are the document formality level, approval completion degree, effective time sequence, and scope coverage relationship.

[0040] Seventh, the coefficient mapping rule base is used to determine the relationship coefficient, effectiveness coefficient, and measure cost impact coefficient. Its sources are the relationship edge type mapping table, the approval status control table, and the corresponding measure cost calculation table in the pricing rule version.

[0041] Through the rule base settings described above, the preset rules, thresholds, and coefficients involved in the embodiments all have clear sources, rather than being arbitrarily set.

[0042] To avoid relying solely on filename or plain text similarity for coarse matching, this embodiment employs event fingerprinting for cost impact identification. The event fingerprint of a cost event unit is represented as follows: ; in: Indicates the first The event fingerprint corresponding to each cost event unit; This represents a deterministic coding function; Indicates the identification of the project object; Indicates the identifier of the list item; Indicates contract section identifier; Indicates the scope of application; Indicates the characteristics of quantity changes; Indicates the time of occurrence; Indicates the approval status; This indicates the source file identifier or source file type identifier.

[0043] To ensure the rules for generating event fingerprints are clear and unambiguous, the system performs unified preprocessing on each field before executing the deterministic encoding function. The preprocessing rules are as follows: The project object identifier, list item identifier, and contract section identifier adopt the unified encoding in the field mapping rule base; The scope of application is indicated in a fixed order of floor, axis, section, and system number; The characteristics of quantitative changes are expressed in order of change type and change value; The occurrence time is expressed in a uniform date format and converted to the corresponding approval cycle, measurement cycle or settlement review cycle according to the business cycle rules; Approval status is mapped to a unified status code according to the approval participation rule base; The source file identifier is formed by a combination of file type, file number, and version number.

[0044] If a field is missing, and the field is a field that can be completed, the field will be marked as to be completed and will not be included in the formal event fingerprint matching. If the field is a required field, the cost event unit will only be included in the list of items to be reviewed and will not be included in the formal propagation calculation.

[0045] 1. How to determine the preset time window: In this embodiment, the preset time window is determined by the business cycle rule base.

[0046] For identifying the common source between design change notices and on-site visa forms, the preset time window adopts the same change approval cycle, that is, the time window boundary is the approval cycle to which the design change confirmation time belongs. For identifying the same source between on-site visa slips and monthly work quantity confirmation slips, the preset time window adopts the same measurement and payment cycle, that is, the start and end dates of monthly measurement are used as the time window boundaries; For identifying the common source between the progress confirmation form and the settlement draft, the preset time window adopts the same settlement review cycle.

[0047] In other words, the preset time window is not a fixed number of days, but is determined based on the existing approval cycle, measurement cycle or settlement review cycle of the project, so as to be consistent with the actual business processing rhythm.

[0048] 2. Preset method for determining associated file combinations: The preset associated file combinations are determined by the file type association rule library, and are established based on the file type relationships that are sequential, mutually referenced, or mutually verified in the actual project management process.

[0049] For example, design change notices and site approval forms are a pre-set combination of related documents, because site approval forms can provide on-site confirmation of the implementation of design changes. On-site visa slips and monthly work quantity confirmation slips are a pre-set combination of related documents, because the monthly work quantity confirmation slip can measure and confirm the new increments generated by visa slips. The progress confirmation form and the settlement draft form are a pre-set combination of related documents, because the settlement draft form is usually based on the results of previous measurement confirmation.

[0050] File types that do not belong to the preset associated file group will not be included in the same-origin relationship determination, even if the same object name appears in the text.

[0051] 3. Homology identification: Two cost event units are considered to have a common origin when they meet the following conditions: First, the identification of the project object, the identification of the list item, the identification of the contract section, and the identification of the scope of application are the same; Second, both events occurred within the same preset time window; Third, the source file types corresponding to both belong to the same preset associated file combination.

[0052] Meeting the above three conditions indicates that the two have a direct relationship in terms of object, scope, time, and business source, and can be regarded as the expression of the same cost item in different business documents.

[0053] 4. Identification of sources of permissible error range and repetition relationships: In this embodiment, the allowable error range is determined by the metrological accuracy rule base, which is based on the metrological units, rules for retaining decimal places, conversion rules, and audit rounding rules stipulated in the contract.

[0054] For example, if a certain item in the list is measured in cubic meters and the contract stipulates that two decimal places are retained, then when comparing the quantity change characteristics between different documents, the result of retaining two decimal places after conversion to a unified unit is used to determine whether they are consistent; the range of differences caused by conversion and rounding is the allowable error range.

[0055] Therefore, the allowable error range is not set arbitrarily, but rather comes from the measurement accuracy rules corresponding to the item in the list.

[0056] When two cost event units have been identified as having the same origin and their quantity change characteristics are consistent, or their quantity change values ​​are within the allowable error range corresponding to the item in the bill of quantities, it is determined that they have a duplicate relationship.

[0057] If the error exceeds the allowable error range, it will not be judged as a duplicate relationship, but will enter the conflict relationship judgment.

[0058] 5. Coverage relationship identification: When two cost event units correspond to the same item in the bill of quantities, and the scope of one cost event unit covers the scope of the other cost event unit, an overlap relationship is determined to exist.

[0059] To avoid misjudging a coverage relationship based solely on the order of time, this embodiment requires that both the attribution and scope of the same list item be satisfied.

[0060] After the coverage relationship is established, the conflict edge control rule base determines which of the following is the low priority cost event node based on the document formality level, approval completion degree, and effective time.

[0061] 6. Conflict Relationship Identification: When two cost event units correspond to the same item in the bill of quantities, and they result in inconsistent pricing basis or inconsistent quantity changes, it is determined that there is a conflict between them.

[0062] Conflict relationships include overriding conflicts, duplication conflicts, rule conflicts, and time conflicts.

[0063] Rule conflicts refer to situations where the same cost event is handled in different documents using different price versions, different quota standards, different fee rules, or different tax rate standards. A time conflict refers to a mismatch between the time when a cost event enters the processing flow and the time when the version or rule takes effect.

[0064] To avoid the approval status being used merely as a descriptive field without clear control implications, this embodiment imposes the following limitations on the conditions for approval status participation: Cost event units that have been approved can directly participate in local propagation recalculation; Cost event units that have been withdrawn, rejected, or pending submission are not included in the partial propagation recalculation. Cost event units awaiting confirmation from supervisors or owners will only be added to the list of items pending review and will not participate in the formal partial recalculation. Cost event units in the partially approved status participate in partial propagation recalculation according to the approved quantity or approved proportion.

[0065] When the original document clearly states the approved quantity, the approved quantity shall replace the original declared quantity; when the original document states the approved percentage, the percentage shall be multiplied by the original declared quantity to obtain the valid quantity; when only partial approval conclusions are given but no specific quantity or percentage is given, the cost event unit shall not be formally recalculated in a partial manner, but shall only be included in the list of items pending review.

[0066] The cost impact graph in this embodiment includes list item nodes, project object nodes, cost event nodes, price version nodes, pricing rule version nodes, and settlement nodes, as well as source relationship edges, substitution relationship edges, supplementary relationship edges, exclusion relationship edges, and amount impact relationship edges connecting each node.

[0067] When constructing the cost map, the system first connects the cost event nodes with the project object nodes and the list item nodes. Then, based on the price information data and pricing rule data, it connects the cost event nodes to the price version nodes and the pricing rule version nodes respectively. Finally, it connects the audit results of each stage to the settlement node.

[0068] In this embodiment, source relationship edges are only used for tracing and do not participate in the propagation of amounts; replacement relationship edges, supplementary relationship edges, exclusion relationship edges, and amount-affecting relationship edges participate in local propagation recalculation.

[0069] For each cost event unit, the system needs to determine its applicable price version node and pricing rule version node.

[0070] The specific process is as follows: First, determine the candidate price versions based on the occurrence time of the cost event unit; Then, determine the candidate pricing rule version based on the approval status and contract terms' effectiveness information; Then, based on the contract segment and the corresponding list item category, the target price version and target pricing rule version are selected from the candidate price version and candidate pricing rule version; When the target price version or target pricing rule version is switched, only the event subgraph associated with the cost event unit is recalculated locally.

[0071] The conditions for switching price versions and rule versions are derived from the effective conditions of contract terms, supplementary agreements, and cost information documents, and are not arbitrarily set by the system.

[0072] To avoid unclear boundaries of the low-priority monetary influence relationship in the claims, this embodiment stipulates that the low-priority monetary influence relationship edge is determined by the conflict edge control rule base, and the determination order is as follows: First, the monetary impact of formally approved documents takes precedence over the monetary impact of provisional confirmation documents. Second, when the documents are equally formal, the monetary impact relationship edge corresponding to the cost event node with a wider coverage takes precedence over the monetary impact relationship edge with a smaller coverage. Third, when the documents are equally formal and have the same coverage, the monetary impact of the cost event node with the later effective date takes precedence over the monetary impact of the earlier effective date. Fourth, if the above conditions still cannot distinguish between them, the edge corresponding to the amount impact relationship of the cost event node with more complete pricing basis identification and clearer approval status shall be given priority.

[0073] The non-priority edges determined according to the above rules are the low-priority monetary influence relationship edges.

[0074] When any cost event unit is added, changed, or withdrawn, the system will use the corresponding cost event node as the starting node and extract the associated event subgraph from the cost impact graph.

[0075] The event subgraph includes associated nodes and associated edges connected to the starting node and whose path length does not exceed a preset level threshold.

[0076] The preset level threshold is determined by the maximum necessary propagation level in the graph pattern, rather than being arbitrarily set.

[0077] In this embodiment, the graph includes at least an event layer, a list layer, a version layer, and a settlement layer. Therefore, the path level threshold should at least cover the necessary path from the starting cost event node to the list item node, the price version node, or the pricing rule version node, and finally to the settlement node.

[0078] If a project adopts a merged version layer data structure, the path level threshold is adjusted according to the maximum necessary propagation level in the project's graph pattern.

[0079] Therefore, the path level threshold comes from the graph structure itself, not from arbitrary empirical values.

[0080] Calculation of the difference in quantities: For the first The difference in quantity for each item in the bill of quantities Represented as:

[0081] in: Indicates the first The difference in quantity for each item in the bill of quantities; Indicates the relationship with the first A set of cost event nodes for each item in the list, where there are edges that influence the amount of the cost. Indicates the first The cost event node for the first The relationship coefficients of each list item node; Indicates the first The effectiveness coefficient of each cost event node; Indicates the first The quantity change value corresponding to each cost event unit. Relationship coefficient. The relationship edge type mapping table in the coefficient mapping rule base is determined as follows: When the The cost event node is supplemented by relation edges to the first... When a new item node in the list has an impact Take the positive one; When the Each cost event node indicates a reduction or cancellation of the original project scope. Take the negative one; When the When the relation edges corresponding to a cost event node are excluded, hidden, or have not yet been qualified to participate in the calculation, Take zero; When a substitution relationship exists, the system will split the pre-substitution event and the post-substitution event into two cost event units, and process them as reduction events and new events respectively.

[0082] Through the above mapping, the relationship coefficients have a clear origin and do not have the problem of arbitrary values. Validity coefficients It is jointly determined by the approval participation rule base and the conflict edge control rule base.

[0083] When the When a cost event unit is in an approved state and the corresponding monetary impact edge is not masked. Choose one; When the When a cost event unit is in a partially approved state Take the ratio of the approved quantity to the declared quantity, or take the approved percentage; When the When a cost event unit is in a pending review, rejected, or withdrawn state, or when its corresponding monetary impact is blocked, Take zero.

[0084] Therefore, the validity coefficient is derived from the approval status and the participation status, rather than from manual designation.

[0085] After determining the difference in the amount of work, the first The difference in amount between each item on the list Represented as:

[0086] in: Indicates the first The difference in amount between each item on the list; Indicates the first The applicable unit price or composite unit price for each item in the list under the current target price version node and target pricing rule version node. The source of the applicable unit price is the target pricing result jointly determined by the price version node and the pricing rule version node.

[0087] Calculation of adjustment results for measures fees: Adjustment results of measures fees Represented as:

[0088] in: This indicates the results of the adjustment of the measures fee; Indicates the number of items on the affected list; Indicates the first The impact coefficient of the measures cost corresponding to each item in the list.

[0089] Impact coefficient of measures cost It is derived from the fee schedule for measures corresponding to the current pricing rule version node, and determined in combination with the list item category, professional category and contract section category.

[0090] For example, the method for calculating the provisional costs corresponding to a certain type of sub-item project is determined by the provisional cost rule table pre-stored in the pricing rule version node. Therefore, the provisional cost impact coefficient comes from the rule table and is not arbitrarily generated.

[0091] Tax adjustment result calculation: Tax adjustment result Represented as:

[0092] in: Indicates the result of tax adjustments; This indicates the applicable tax rate parameter under the current pricing rule version node.

[0093] Tax rate parameters The tax rate is derived from the corresponding tax rate rule in the current pricing rule version node, and is not estimated separately by the system.

[0094] Conflict edge control logic: For cost event nodes that have overlapping conflicts, the low-priority amount impact relationship edge corresponding to the covered cost event node is temporarily blocked. For cost event nodes with duplicate conflicts, the edges corresponding to the duplicate amount impact relationships in the duplicate cost event nodes are temporarily masked. For cost event nodes with rule conflicts or time conflicts, the corresponding monetary impact edges will not participate in local propagation recalculation until the conflict determination is completed.

[0095] After the conflict is resolved, the system restores the monetary influence relationships that meet the conditions based on the conflict control rule base and participates in the calculation.

[0096] Phased cost snapshot and evidence chain result package: After each local propagation recalculation is completed, the system generates a phased cost snapshot. The phased cost snapshot records at least the set of affected list items, the set of associated cost events, the applicable price version, the applicable pricing rule version, the difference in quantities, the adjustment result of the measures fee, the adjustment result of the tax, the snapshot generation time, and the identifier of the starting cost event node that triggered this snapshot.

[0097] When new, changed, or withdrawn events occur again, the system extracts a new event subgraph based on the previous stage cost snapshot and performs incremental recalculation.

[0098] When outputting items to be reviewed, suspected duplicate pricing, suspected omissions, and suspected rule application issues, the system simultaneously generates an evidence chain result package. The evidence chain result package is a structured data object, including at least the source file identifier field, event fingerprint field, version application field, propagation path field, conflict determination field, and amount difference field.

[0099] The propagation path field records the propagation order from the initial cost event node to the list item node, version node, and settlement node; the conflict determination field records the determination results of coverage conflict, duplicate conflict, rule conflict, or time conflict; and the amount difference field records the amount difference of each affected list item, the adjustment result of the measure fee, and the adjustment result of the tax.

[0100] A specific application process example: During the construction phase of a certain construction project, the project first generates a bill of quantities and a construction contract. Based on this, the system establishes nodes for bill of quantities items, contract segments, and initial price versions.

[0101] Subsequently, the design unit issued a design change notice involving adjustments to the construction practices of a certain zone. During the construction process, the supervision and construction units formed on-site visa forms for the local implementation. Monthly quantities confirmation forms were formed during monthly measurements, and a settlement draft was formed during the settlement review stage.

[0102] After receiving the above files, the system first extracts and merges the project object identifier, list item identifier, contract section identifier, scope identifier, quantity change characteristics, pricing basis identifier, occurrence time, approval status, and source file identifier according to the field mapping rule library to form the corresponding cost event unit.

[0103] If the design change notice and the site visa form correspond to the same project object, the same list item, and the same scope of application, and are both within the same change approval cycle, and their document types belong to the same pre-set associated document combination, then they are determined to have a common source relationship.

[0104] If a partial item in the on-site visa form is later completely covered by the formal design change, the system will identify the coverage relationship and, according to the conflict edge control rule library, shield the low-priority amount impact relationship edge corresponding to the covered cost event node.

[0105] If the monthly work quantity confirmation form records the same new work quantity again, and the difference falls within the allowable error range determined by the measurement accuracy rule library, it is determined that it has a duplicate relationship with the aforementioned items, and the duplicate amount impact relationship edge is masked.

[0106] If the settlement draft uses a price version that is inconsistent with the supplementary agreement, a rule conflict is identified. Before the rule conflict is confirmed, the part of the amount affecting the relationship edge will not participate in the local propagation recalculation.

[0107] Then, starting from the latest cost event node that has changed, the system extracts the event subgraph, calculates the difference in quantity and amount of the affected list items according to the above formula, and then generates a phased cost snapshot and evidence chain result package by combining the measure fee table and tax rate rule table.

[0108] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. An information management method for engineering cost, characterized in that, Includes the following steps: S1: Obtain the bill of quantities data, contract data, design change data, site visa data, progress confirmation data, settlement data, price information data, and pricing rule data corresponding to the target project, and standardize the obtained data according to the unified field specification to form multiple cost event units. Each cost event unit includes the project object identifier, bill of quantities item identifier, contract section identifier, scope identifier, quantity change characteristics, pricing basis identifier, occurrence time, approval status, and source document identifier. S2: Based on the engineering object identifier, list item identifier, contract section identifier, scope identifier, quantity change characteristics, occurrence time, approval status and source document identifier of each cost event unit, generate the corresponding event fingerprint according to the preset combination rules, and identify the same source relationship, duplicate relationship, coverage relationship and conflict relationship between cost event units according to the event fingerprint and the preset matching rules. S3: Based on the correspondence between each cost event unit and the bill of quantities, as well as the identified common source relationship, duplicate relationship, coverage relationship and conflict relationship, construct the cost impact map. The cost impact map includes bill of quantities item nodes, engineering object nodes, cost event nodes, price version nodes, pricing rule version nodes and settlement nodes, as well as source relationship edges, substitution relationship edges, supplementary relationship edges, exclusion relationship edges and amount impact relationship edges connecting each node; S4: For each cost event unit, based on its occurrence time, approval status, contract clause effectiveness information, contract segment to which it belongs and corresponding list item category, determine the corresponding price version node and pricing rule version node from the price information data and pricing rule data, and write the determination results into the cost impact map. S5: When any cost event unit is added, changed, or withdrawn, the corresponding cost event node is taken as the starting node, the event subgraph associated with the starting node is extracted, and local propagation recalculation is performed along the substitution relationship edge, supplementary relationship edge, exclusion relationship edge and amount influence relationship edge in the event subgraph to determine the scope of affected list items, quantity difference, applicable price version, measure fee adjustment result and tax adjustment result, and generate the corresponding stage cost snapshot; S6: Based on the identification results of duplicate relationships, coverage relationships, and conflict relationships, as well as the local propagation recalculation results and the phased cost snapshot, output the corresponding items to be audited, duplicate pricing doubts, omission doubts, and rule application doubts, and simultaneously generate an evidence chain result package for each item to be audited. The evidence chain result package includes at least the source file identifier field, event fingerprint field, version application field, propagation path field, conflict determination field, and amount difference field.

2. The information management method for engineering cost as described in claim 1, characterized in that, The standardization process for the acquired data according to a unified field specification specifically includes: Extract the following information from contract data, design change data, site visa data, progress confirmation data, and settlement data: project object identification information, list item identification information, contract section identification information, scope identification information, quantity change characteristics, occurrence time information, approval status information, and source document identification information. According to the preset mapping rules, fields with different names in different data sources are converted into unified field names and written to the corresponding cost event units; For data items that cannot be directly mapped to the bill of quantities, an association mapping relationship between them and the target bill of quantities items is established based on the project object identifier, scope identifier, and contract section identifier.

3. The information management method for engineering cost as described in claim 2, characterized in that, Based on the event fingerprint and preset matching rules, the relationships of homology, duplication, overlap, and conflict between cost event units are identified, specifically including: When two cost event units have the same project object identifier, list item identifier, contract section identifier, and scope identifier, their occurrence time is within a preset time window, and their corresponding source file types belong to a preset associated file combination, it is determined that the two have a common source relationship. When two cost event units have a common origin and consistent quantity change characteristics, it is determined that the two have a duplicate relationship; When two cost event units correspond to the same item in the bill of quantities, and the scope of one cost event unit covers the scope of the other cost event unit, it is determined that there is an overlap relationship between the two. When two cost event units correspond to the same item in the bill of quantities, and they result in inconsistent pricing basis or inconsistent quantity changes, it is determined that there is a conflict between them.

4. The information management method for engineering cost as described in claim 3, characterized in that, The conflict relationships include overlay conflicts, duplication conflicts, rule conflicts, and time conflicts; For cost event nodes that have overlapping conflicts, the low-priority amount impact relationship edge corresponding to the covered cost event node is temporarily blocked. For cost event nodes with duplicate conflicts, the edges corresponding to the duplicate amount impact relationships in the duplicate cost event nodes are temporarily masked. For cost event nodes with rule conflicts or time conflicts, the corresponding monetary impact edges will not participate in local propagation recalculation until the conflict determination is completed.

5. The information management method for engineering cost as described in claim 4, characterized in that, The process of determining the corresponding price version node and pricing rule version node based on its occurrence time, approval status, contract clause effectiveness information, contract segment, and corresponding list item category specifically includes: Candidate price versions are determined based on the occurrence time of cost event units; The candidate pricing rule version is determined based on the approval status and contract terms effectiveness information; Based on the contract section and corresponding list item category, filter the target price version and target pricing rule version from the candidate price version and candidate pricing rule version; When the target price version or target pricing rule version is switched, only the event subgraph associated with that cost event unit is recalculated locally.

6. The information management method for engineering cost according to claim 5, characterized in that, Extract the event subgraph associated with the starting node, specifically including: Using the starting node as the center node, extract the associated nodes and associated edges that are connected to the starting node and whose path length does not exceed a preset level threshold; The extracted associated nodes and edges are used to construct an event subgraph for local propagation recalculation. The phased cost snapshot records at least the set of affected list items, the set of related cost events, the applicable price version, the applicable pricing rule version, the difference in quantities, the adjustment results of the measures fee, and the adjustment results of taxes at the corresponding time.

7. The information management system for engineering cost is applicable to the information management method for engineering cost as described in any one of claims 1-7, characterized in that, include: Includes memory, processor, and computer programs stored in memory and capable of running on the processor; When the processor executes the computer program, it is also used to: The acquired contract data, design change data, site visa data, progress confirmation data, and settlement data are processed to extract field information, including project object identification information, list item identification information, contract section identification information, scope identification information, quantity change characteristics information, occurrence time information, approval status information, and source document identification information. Convert fields with different names from different data sources to a unified field name according to the preset mapping rules; Establish a mapping relationship between the project object identifier, scope identifier, and contract section identifier and the target list items.

8. The information management system for engineering cost estimation according to claim 7, characterized in that, When the processor executes the computer program, it is also used to: The event fingerprint is generated by combining the project object identifier, list item identifier, contract section identifier, scope identifier, quantity change characteristics, occurrence time, approval status, and source document identifier according to the preset combination rules. Based on the event fingerprint, the homology, duplication, overlay and conflict relationships between cost event units are identified. Based on the identified homologous, duplicate, overlapping, and conflicting relationships, the corresponding monetary impact edges in the cost impact map are either masked or restored.

9. The information management system for engineering cost estimation according to claim 8, characterized in that, When the processor executes the computer program, it is also used to: When any cost event unit is added, changed, or withdrawn, the event subgraph associated with the corresponding cost event node is extracted; Local propagation recalculation is performed within the event subgraph along the substitution, supplementary, exclusionary, and monetary influence edges. Generate an evidence chain result package that includes source file identifier field, event fingerprint field, version applicable field, propagation path field, conflict determination field, and amount difference field.

Images