A design cost linkage management method and system based on power transmission and transformation engineering design knowledge graph

Abstract

The application relates to the technical field of power transmission and transformation engineering design and cost management, and discloses a design cost linkage management method and system based on a power transmission and transformation engineering design knowledge graph, which comprises the following steps: in response to a power transmission and transformation engineering cost evaluation request, obtaining engineering design elements and target region condition groups of an engineering to be evaluated; calling a power transmission and transformation engineering design knowledge graph, mapping the engineering design elements into a standardized design subgraph; traversing graph objects in the standardized design subgraph, and marking region sensitive relationships; calling a source region engineering subgraph, constructing a ladder type migration chain, and along the ladder type migration chain, reusing migratable structure units and calibrating the region sensitive relationships, and outputting a cost evaluation result. The application can realize cross-region cost experience migration when target region samples are insufficient, and can improve the interpretability and stability of region difference calibration.

Description

Technical Field

[0001] This invention relates to the field of power transmission and transformation engineering design and cost management technology, and in particular to a design and cost linkage management method and system based on a power transmission and transformation engineering design knowledge graph. Background Technology

[0002] The cost of power transmission and transformation projects is influenced by a variety of factors, including project scale, design scheme, equipment and materials, construction environment, market prices, and local policies. Related technologies typically employ methods such as historical sample statistics, indicator calculation, regression prediction, or big data modeling to extract cost indicators or influencing factors from historical projects and predict the costs of the project to be evaluated.

[0003] However, for cross-regional power transmission and transformation projects, similar projects often exhibit significant cost differences in different regions. These differences stem not only from variations in price levels but also from factors such as natural conditions, construction limitations, design constraints, and local policies. For instance, high-altitude areas may necessitate adjustments to equipment selection, permafrost regions may alter the amount of foundation work, mountainous transportation conditions may affect the cost of equipment and materials arriving on-site, and different land acquisition regulations may influence other costs associated with the transmission line project.

[0004] If historical samples from different regions are directly used to train the cost model, the aforementioned regional differences can easily be compressed into unexplainable statistical errors. If separate models are built for different regions, they are easily limited by insufficient sample size, uneven project types, and incomplete coverage of design conditions. Related technologies struggle to effectively separate reusable design commonalities from regional differences that require calibration, resulting in insufficient stability and interpretability of cross-regional cost migration. Summary of the Invention

[0005] This invention provides a design cost linkage management method and system based on a knowledge graph of power transmission and transformation engineering design. It aims to solve the technical problems in cross-regional power transmission and transformation engineering cost assessment, where directly reusing historical samples can easily lead to regional bias, while zonal modeling is easily limited by insufficient samples.

[0006] To achieve the above objectives, this invention provides a design cost linkage management method based on a knowledge graph for power transmission and transformation engineering design, the method comprising the following steps: In response to a request for cost assessment of power transmission and transformation projects, obtain the engineering design elements and target area condition groups of the project to be assessed; The power transmission and transformation engineering design knowledge graph is invoked to map the engineering design elements into standardized design subgraphs; Traverse the atlas objects in the standardized design sub-graphs and mark the region sensitive relationships. The region sensitive relationships are written by the design condition grid to the influence position between the region condition group and the atlas objects. The atlas objects include design nodes, design relationships and cost items. Retrieve the engineering sub-map of the source region, construct a stepped migration chain, reuse the migrateable structural units along the stepped migration chain and calibrate the region sensitivity relationship, and output the cost assessment result.

[0007] To achieve the above objectives, the present invention also provides a design cost linkage management system based on a knowledge graph of power transmission and transformation engineering design, comprising: The acquisition module is used to obtain the engineering design elements and target area condition groups of the project to be evaluated in response to the request for cost assessment of power transmission and transformation projects. The calling module is used to call the knowledge graph of power transmission and transformation engineering design and map the engineering design elements into standardized design subgraphs. The traversal module is used to traverse the atlas objects in the standardized design sub-graph and mark the region sensitive relationships. The region sensitive relationships are written by the design condition grid to the influence position between the region condition group and the atlas object. The atlas object includes design nodes, design relationships and cost items. The output module is used to retrieve the engineering sub-map of the source area, construct a stepped migration chain, reuse the migrateable structural units along the stepped migration chain and calibrate the area sensitivity relationship, and output the cost assessment result.

[0008] One or more technical solutions proposed in this application have at least the following technical effects: Compared to related technologies that directly train cost models using cross-regional historical samples or train cost models separately for different regions, this application first maps the project to be evaluated into standardized design sub-graphs, and then marks regional sensitive relationships through design condition grids. This allows the commonalities in engineering design and regional differences to be separated and processed in different map objects. As a result, transferable structural units can reuse historical cost items, and regional sensitive relationships can be calibrated independently, avoiding the compression of regional differences into a single correction coefficient. Simultaneously, this application hierarchically organizes the source region's engineering sub-graphs through a step-by-step migration chain. When the target region's samples are insufficient, basic cost experience can be provided first by engineering sub-graphs with consistent hard engineering conditions, and then sensitive relationship calibration can be performed by engineering sub-graphs with similar regional conditions, making cross-regional cost experience transfer more stable. Furthermore, after obtaining the migrated and calibrated cost items, this application performs a reverse backtracking consistency check, which can detect whether the calibrated cost items disrupt the cost structure and design constraints of the source region's projects, thereby reducing the risks of over-calibration, abnormal calibration, and sample mis-migrating. Attached Figure Description

[0009] Figure 1 This is a flowchart illustrating the design cost linkage management method based on a knowledge graph of power transmission and transformation engineering design, as described in an embodiment of the present invention.

[0010] Figure 2 This is a schematic diagram illustrating the principle structure of the stepped migration chain in an embodiment of the present invention.

[0011] Figure 3 This is a schematic diagram of the design cost linkage management system based on the knowledge graph of power transmission and transformation engineering design, as described in an embodiment of the present invention. Detailed Implementation

[0012] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application. To better understand the technical solutions of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0013] The main solution of this application embodiment is as follows: In response to a request for cost assessment of a power transmission and transformation project, the engineering design elements and target area condition groups of the project to be assessed are obtained; the power transmission and transformation project design knowledge graph is invoked to map the engineering design elements into standardized design subgraphs; the graph objects in the standardized design subgraphs are traversed, and the regional sensitive relationships are marked, wherein the regional sensitive relationships are written by the design condition grid to the influence position between the regional condition groups and the graph objects, and the graph objects include design nodes, design relationships, and cost items; the source area engineering subgraph is retrieved, a step-by-step migration chain is constructed, and the transferable structural units are reused and the regional sensitive relationships are calibrated along the step-by-step migration chain to output the cost assessment results.

[0014] In related technologies, cost assessment for power transmission and transformation projects typically relies on historical samples, cost indices, or statistical models. While this approach has some usability within the same region, it has significant limitations when migrating across regions. This is because cross-regional differences are not merely price differences, but rather the result of the combined effects of design objectives, construction constraints, market conditions, and policy boundaries. While compressing these differences into a single coefficient simplifies the calculation process, it fails to explain why a particular cost has changed, nor can it determine whether that change should apply to a specific design component.

[0015] This application uses a knowledge graph of power transmission and transformation engineering design as an intermediate expression layer for cross-regional cost transfer. The system first converts engineering data from different regions into unified standardized design sub-graphs, and then distinguishes between transferable structural units and region-sensitive relationships within these standardized design sub-graphs. Transferable structural units are used to incorporate reusable design experience and cost items from projects in the source region, while region-sensitive relationships are used to incorporate cost items that need to be adjusted according to changes in the conditions of the target region.

[0016] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, knowledge graph query, engineering cost calculation, and network communication functions, such as a server, cloud computing platform, engineering cost workstation, or a cost management system capable of performing the above functions. The following description uses a cost management system as an example to illustrate this embodiment and the subsequent embodiments.

[0017] Based on this, embodiments of this application provide a design cost linkage management method based on a knowledge graph for power transmission and transformation engineering design. (Refer to...) Figure 1 In this embodiment, the cost management method includes steps S100-S500: Step S100: In response to the request for cost assessment of power transmission and transformation projects, obtain the engineering design elements and target area condition group of the project to be assessed.

[0018] It should be noted that engineering design elements characterize the design structure and pricing objects of the project to be evaluated, and may include project type information, project scale information, component parameter information, and constraint parameter information. The target area condition group characterizes the external influencing conditions of the area where the project to be evaluated is located, and may include natural conditions, market prices, construction environment, and policy conditions. For example, for a 220kV substation project, engineering design elements may include site type, main transformer scale, distribution equipment type, civil engineering structure type, and equipment installation objects; the target area condition group may include altitude range, seismic fortification requirements, local material price level, equipment transportation radius, construction season restrictions, and local cost boundaries. After receiving the cost evaluation request, the system first performs field validation, unit conversion, and standardization on the above data.

[0019] In one feasible implementation, the system can set the following coding format for engineering design elements: project type code, component object code, design constraint code, and cost object code. Taking a power line project as an example, the project type code can represent overhead lines or cable lines; the component object code can represent objects such as poles, foundations, conductors, grounding, and ancillary facilities; the design constraint code can represent constraints such as terrain, icing, wind zones, and construction access; and the cost object code can represent objects such as building construction costs, installation costs, equipment purchase costs, and other costs. Through this coding format, the system can ensure that design data from different source files are processed in a unified manner.

[0020] Step S200: Call the power transmission and transformation engineering design knowledge graph to map the engineering design elements into standardized design subgraphs.

[0021] It is understandable that the way data is expressed in different historical engineering documents is often inconsistent. For example, the same design component may be named differently in different design unit documents, and the same cost object may be classified at different levels in different pricing documents. If the original data is used directly for cross-regional migration, it will lead to inaccurate calculation of structural similarity, which in turn will affect the reuse of cost experience.

[0022] This application utilizes a knowledge graph for power transmission and transformation engineering design to standardize the mapping of engineering design elements. The knowledge graph pre-stores the relationships between design entities, constraints, and cost objects. The system maps the original fields in the project to be evaluated to standard component nodes, the project scale and construction restrictions to standard constraints, and the quantity items and pricing items to corresponding cost items, ultimately resulting in a standardized design sub-graph.

[0023] For example, when different descriptions appear in the project to be evaluated, such as "outdoor GIS power distribution equipment," "outdoor gas-insulated switchgear area," and "GIS outdoor layout," the system can use a knowledge graph design to uniformly map them to the same type of standard component node, while retaining their layout type, equipment level, and corresponding cost object. As another example, when the "earthwork volume" in a historical project and the "site leveling and excavation volume" in the project to be evaluated belong to the same cost object but have different definitions, the system can use constraints to complete their conversion relationship, avoiding cost discrepancies caused by direct reuse.

[0024] In this embodiment, the standardized design sub-graph includes at least three types of graphical objects. The first type is design nodes, used to represent engineering components and design objects; the second type is design relationships, used to represent the interaction relationships between components, between components and constraints, and between components and costs; the third type is cost items, used to represent quantities, prices, and cost categories. Through these three types of graphical objects, the system can transform engineering design information and cost information from tabular data into transferable, calibrable, and interpretable graphical structure data.

[0025] Step S300: Traverse the graph objects in the standardized design subgraph and mark the sensitive relationships of the regions.

[0026] It should be noted that regionally sensitive relationships refer to the graphical relationships that may cause changes in cost items when the target region's condition group changes. Unlike the traditional approach of treating regional differences as an overall coefficient, this application uses a design condition grid to write the influence position between the regional condition group and the graphical object, enabling regional differences to be located at specific design nodes, design relationships, and cost items.

[0027] The design condition grid uses regional condition groups as the row dimension and map objects as the column dimension. Each cell contains the sensitivity level, migration attribute, and cost range. The sensitivity level can include weak sensitivity, medium sensitivity, and strong sensitivity; the migration attribute can include direct reuse, local calibration, and prohibit migration; the cost range is used to limit the cost objects that can be affected by changes in the regional conditions corresponding to that cell.

[0028] For example, in mountainous line projects, the construction environment layer and the tower foundation can be marked as highly sensitive, and the cost range can be limited to the cost of foundation excavation, material transportation, and construction measures; the market price layer and the conductor can be marked as moderately sensitive, and the cost range can be limited to the material price difference and transportation price difference; the policy conditions layer and the equipment purchase can usually be marked as weakly sensitive, because policy conditions have more impact on land acquisition compensation, crossing compensation, or local costs.

[0029] The design condition grid serves to pre-structure the influence relationships between regional conditions and map objects. When traversing standardized design sub-maps, the system does not need to perform global corrections on all cost items. Instead, it directly identifies the affected map objects based on the design condition grid and writes their sensitivity levels and cost ranges. This reduces the range of erroneous corrections and improves the interpretability of the calibration process.

[0030] In one feasible implementation, the system can set update rules for the design condition grid. When the condition group of the target area changes, the system first determines the condition layer to which the change belongs, and then only updates the grid data under the corresponding condition layer. If only the market price changes in the target area, the system only updates the grids corresponding to the market price layer, without recalculating the natural condition layer and the policy condition layer; if the altitude range changes in the target area, the system only updates the grids in the natural condition layer related to equipment selection, insulation configuration, and construction measures. Through partial updates, the system can reduce redundant calculations and maintain the stability of the cost assessment results.

[0031] In one feasible implementation, the system calculates the sensitivity level of each cell based on the conditional difference, the type of object affected, and the cost mapping relationship. Specifically, the system first reads the conditional values ​​of the target area, the conditional values ​​of the source area, and the corresponding baseline interval, and calculates the conditional offset. Then, it reads the cost impact type corresponding to the map object. If the condition can change the design selection, engineering quantity, or mandatory construction scheme, a structural impact identifier is written. If the condition only changes the unit price of materials, labor, machinery, or transportation, a price impact identifier is written. If the condition only changes local fees or compensation boundaries, a policy impact identifier is written. The system writes the sensitivity level as 0 to 3 according to the conditional offset and impact identifier: 0 or 1 is written when the conditional offset is less than the first threshold and there is no structural impact; 2 is written when the conditional offset is between the first and second thresholds; and 3 is written when the conditional offset exceeds the second threshold or there is a mandatory design change. The first and second thresholds are pre-configured according to the condition type, for example, altitude, permafrost, transportation radius, seismic fortification, and policy costs correspond to different threshold tables.

[0032] Migration attributes are written based on sensitivity level and cost impact type. When the sensitivity level is 0 or 1 and the cost scope is consistent, the migration attribute is directly reused; when the sensitivity level is 2 or only price or policy impact exists, the migration attribute is written for local calibration; when the sensitivity level is 3 and the structural impact identifier is valid, the migration attribute is written as "migration prohibited". The cost scope is jointly defined by the cost object code and condition impact type of the map object: natural conditions affect engineering quantities and measure costs, market prices affect material costs, labor costs, machinery costs, and transportation costs, and policy conditions affect compensation costs and local costs among other costs. If the same condition maps to multiple cost objects simultaneously, the system only writes the cost scope that has a direct cost attribution relationship or constraint relationship with the map object.

[0033] Step S400: Retrieve the engineering sub-map of the source region, construct a stepped migration chain, reuse the migrateable structural units along the stepped migration chain and calibrate the region sensitivity relationship, and output the cost assessment result.

[0034] It should be noted that the aforementioned stepped migration chain has a chain-like hierarchy consisting of a strong constraint layer, a price adaptation layer, and a policy correction layer. Each subsequent chain-like hierarchy only receives verified transferable structural units and converged regionally sensitive relationships from the preceding chain-like hierarchy. It is understood that the source region engineering submap is standardized map data read from a historical engineering database. Traditional methods typically select a most similar historical engineering project as a reference object, or perform a weighted average of multiple historical engineering samples. However, in cross-regional cost assessment, individual historical engineering projects may have similar design structures but significantly different regional conditions, or they may have similar regional conditions but insufficiently similar design structures. Directly selecting a source project can easily lead to migration bias.

[0035] This application organizes the source region engineering sub-maps into a stepped migration chain. The stepped migration chain can include a strong constraint layer, a price adaptation layer, and a policy correction layer. The strong constraint layer ensures consistency in project type, design safety boundaries, and major structural dimensions; the price adaptation layer calibrates market conditions such as material prices, labor prices, machinery prices, and transportation prices; and the policy correction layer incorporates policy conditions such as land acquisition compensation, crossing compensation, and local cost boundaries. Through this chain-like hierarchy, the system can decompose the migration process into multiple continuous and constrained processing stages.

[0036] In one feasible implementation, the system first reads the historical project sub-graph set and deletes historical project sub-graphs whose hard engineering conditions are inconsistent with those of the project to be evaluated. Hard engineering conditions may include project type, main voltage level, main equipment level, line loop attributes, and mandatory safety boundaries. This deletion process is used to prevent projects with inconsistent structural premises from entering the migration chain.

[0037] The system then calculates the graph structure similarity between the remaining historical project subgraphs and the standardized design subgraphs. Graph structure similarity can be characterized by node coverage, relationship consistency, cost object matching, and constraint consistency. In one example, a structure similarity threshold of 0.75 can be set; if the structure similarity between a candidate project subgraph and a standardized design subgraph is lower than 0.75, the candidate project subgraph will not be included in the chain-level sorting. The above threshold can be adjusted according to the project stage and data completeness.

[0038] In one feasible implementation, the structural similarity S can be calculated as S = 0.35 × node coverage rate + 0.25 × relationship consistency rate + 0.20 × cost item coverage rate + 0.20 × pricing caliber consistency rate. The node coverage rate represents the proportion of comparable nodes in the standardized design sub-graph covered by the candidate project sub-graph; the relationship consistency rate represents the degree of consistency in subordinate relationships, constraint relationships, and cost attribution relationships; the cost item coverage rate represents the range of cost objects that the candidate project sub-graph can provide; and the pricing caliber consistency rate represents the degree of consistency in the unit of work volume, cost level, and fee calculation caliber. If any single indicator is lower than the corresponding minimum threshold, even if the overall structural similarity reaches the threshold, the candidate project sub-graph will not be written into the first chain level.

[0039] The system hierarchically arranges historical project sub-graphs that meet similarity thresholds according to the constraint strength of regional condition groups. Constraint strength can be reflected in whether it affects the design structure, the quantity of work, or only the cost boundary. Conditions affecting the design structure enter the strong constraint layer, conditions primarily affecting market prices enter the price adaptation layer, and conditions primarily affecting local cost boundaries enter the policy adjustment layer. This arrangement allows the step-by-step migration chain to operate in the order of locking the structure, calibrating the price, and adjusting the boundary.

[0040] In one feasible implementation, the constraint strength of the regional condition group is jointly determined by the design structure impact level, cost impact level, and policy boundary impact level. The design structure impact level is used to determine whether the regional conditions change the selection of electrical equipment, foundation type, tower type, construction scheme, or mandatory safety boundary; the cost impact level is used to determine whether the regional conditions only change the unit price of materials, labor, machinery, or transportation; and the policy boundary impact level is used to determine whether the regional conditions only change the cost range of land acquisition, crossing, and regulatory fees. If the candidate historical project sub-map and the project to be evaluated reach the same threshold in terms of design structure impact level, it is written into the strong constraint layer; if their structures are consistent and the price condition distance is less than the price threshold, it is written into the price adaptation layer; and if their structures are consistent and can provide a policy cost range, it is written into the policy correction layer. When a candidate historical project sub-map simultaneously meets multiple level conditions, it is written first in the order of strong constraint layer, price adaptation layer, and policy correction layer, and the unused condition capabilities are used as backup calibration information under that level.

[0041] It should be noted that passing the consistency verification means that the node coverage rate, relationship consistency rate, cost object matching rate, and pricing caliber consistency rate of the transferable structural unit are all not lower than the corresponding thresholds, and the transferable structural unit is not marked as strongly sensitive by the design condition grid. Convergence means that the difference in correction amounts for sensitive relationships in the same region during two consecutive calibrations is less than the convergence threshold, or the correction amount has fallen within the cost range boundary and no longer triggers mutually exclusive corrections. If different source region engineering sub-graphs provide conflicting cost items or sensitive relationships for the same cost object, the system first selects the result with higher priority at the chain level; if they are at the same level, it selects the result with higher graph structure similarity; if the similarity difference is less than a preset difference, the median value within the cost range boundary is used, and the source of the conflict is recorded.

[0042] like Figure 2 As shown, in the strong constraint layer, the system locks the transferable structural units that meet the hard engineering conditions and writes them into the corresponding basic cost items. A transferable structural unit is a set of graphical objects with consistent structural, functional, and pricing specifications. For example, in a substation project of the same voltage level, if the equipment combination, installation relationship, and pricing specification of a typical bay are consistent, then that typical bay can be reused as a transferable structural unit.

[0043] In the price adaptation layer, the system reads the price conditions of the target area and writes the difference correction amount for price-sensitive relationships. For example, if the unit price of a certain type of land material in the source area is 150 yuan per unit, and the unit price of the same type of land material in the target area is 180 yuan per unit, and the corresponding cost object belongs to the price-sensitive relationship marked by the design condition grid, then the system will write a difference of 30 yuan per unit into the corresponding cost item, instead of proportionally amplifying all civil engineering costs. If the transportation radius changes from 80 kilometers to 150 kilometers, the system can write the correction amount only for the cost of equipment and materials arriving on site, based on the cost range limited by the transportation condition grid.

[0044] In the policy correction layer, the system reads the cost boundaries of the target area and writes the boundary correction amounts to the policy-sensitive relationships. For example, if a target area sets an upper limit range for compensation for railway corridors, the system writes this range into the cost object corresponding to the policy-sensitive relationship and restricts it from being applied to equipment purchase costs or installation engineering costs. In this way, policy-related costs will not be mistakenly transferred to technical costs.

[0045] Finally, the system merges the basic cost item, the difference correction amount, and the boundary correction amount to obtain the migration calibration cost item, and summarizes them to obtain the cost assessment result. This result may include the total cost, the cost of each item, the description of the main sensitive relationships, and the description of the migration source. The description of the main sensitive relationships is used to indicate the costs affected by the target area condition group; the description of the migration source is used to indicate the migrateable structural units from the engineering sub-drawing of a certain source area.

[0046] Based on the first embodiment of this application, in the second embodiment of this application, the same or similar content as the above embodiment can be referred to the above description, and will not be repeated hereafter. On this basis, the knowledge graph of power transmission and transformation engineering design in the embodiments of the present invention can be constructed in the following manner.

[0047] The cost management system collects historical engineering data from power transmission and transformation projects. This data collection covers design data, inventory data, pricing data, and regional data. Design data is used to extract project type, design scale, component objects, and constraint parameters; inventory data is used to extract equipment and material objects; pricing data is used to extract quantities, prices, and expense items; and regional data is used to extract natural conditions, market prices, construction environment, and policy conditions.

[0048] The system analyzes the engineering design elements in the engineering data set and uniformly encodes synonymous elements, homonymous elements, and default elements. For example, "high altitude correction," "altitude correction," and "plateau correction" are merged into the same constraint code; "equipment transportation cost," "material transportation cost," and "on-site transportation cost" are merged into the transportation cost object; and default cost objects that can be deduced from upstream and downstream relationships are filled into the corresponding map positions.

[0049] The system categorizes the coded engineering design elements into design entities, constraints, and cost objects. Design entities describe the components or equipment in power transmission and transformation projects; constraints describe the regional or regulatory conditions affecting the design entities; and cost objects describe the quantities, prices, or expense items that can be included in cost assessments. The system records the relationships between these three elements, forming a knowledge graph for power transmission and transformation engineering design.

[0050] In one feasible implementation, a three-part graphical structure can be set up: design entity, constraint relationship, and cost object. Taking a power line tower foundation as an example, the tower foundation is the design entity, the terrain conditions and construction environment are the constraint relationships, and the foundation engineering quantity and transportation costs are the cost objects. When the terrain conditions of the target area change, the system can find the affected cost objects along the constraint relationships without having to re-traverse all engineering costs. This three-part structure distinguishes this application from simple table associations or ordinary index libraries.

[0051] Based on the first embodiment of this application, in the third embodiment of this application, the same or similar content as the above embodiment can be referred to the above description, and will not be repeated hereafter. On this basis, the design condition grid in the embodiment of the present invention can be further processed as follows.

[0052] The design condition grid consists of a region condition group, a map object, a sensitivity level, migration attributes, a cost range, and an update status. The region condition group represents the source of external influence; the map object represents the affected design node, design relationship, or cost item; the sensitivity level represents the intensity of the influence; the migration attribute indicates whether the object corresponding to the grid can be directly reused; the cost range limits the location of the correction; and the update status indicates whether the grid needs to be recalculated due to changes in the target region conditions.

[0053] For example, the sensitivity level can be set to a range of 0 to 3. 0 represents no sensitivity, 1 represents weak sensitivity, 2 represents medium sensitivity, and 3 represents strong sensitivity. When the sensitivity level of a cell is 3, the system does not allow its corresponding map object to directly enter the strong constraint layer as a transferable structural unit; when the sensitivity level is 2, the system allows it to enter the migration chain, but local calibration must be performed at the price adaptation layer or policy correction layer; when the sensitivity level is 1, the system can directly reuse the source region cost item while retaining the notes.

[0054] Furthermore, the design condition grid can set cost scope boundaries. For example, for high-altitude conditions under the natural conditions layer, the cost scope can be limited to equipment selection costs, installation costs, and testing and commissioning costs; for transportation conditions under the construction environment layer, the cost scope can be limited to material delivery costs and large equipment transportation costs; for local regulations under the policy conditions layer, the cost scope can be limited to policy-related costs among other costs. By using cost scope boundaries, the system can prevent the same condition change from simultaneously and incorrectly correcting multiple irrelevant cost objects.

[0055] Compared to traditional regional coefficient tables, design condition grids offer two advantages. First, they specify regional conditions at the point of influence between map objects, rather than at the project-level parameter level. Second, they support local updates; when a condition layer in the target regional condition group changes, only the relevant grid is updated, without triggering a recalculation of all cost items. This approach improves the accuracy and efficiency of cross-regional cost migration.

[0056] Based on the first embodiment of this application, in the fourth embodiment of this application, the same or similar content as the above embodiment can be referred to the above description, and will not be repeated hereafter. On this basis, the ladder migration chain in the embodiments of the present invention can further perform the following processing.

[0057] The cost management system first performs a hard engineering condition screening on the historical project sub-drawing set. Hard engineering conditions refer to conditions that, once inconsistent, are unsuitable for design experience transfer, such as project type, main voltage level, main equipment level, line loop attributes, and mandatory safety boundaries. The screened historical project sub-drawings are then added to the candidate set.

[0058] The system calculates graph structure similarity for candidate sets. Graph structure similarity can be characterized as follows: node coverage rate indicates the proportion of the project's graph objects to be evaluated that are covered by historical project subgraphs; relationship consistency rate indicates the degree of consistency of design relationships in the two types of subgraphs; cost object matching rate indicates the coverage of reusable cost objects; and constraint caliber consistency rate indicates whether the quantities or pricing calibers are consistent. The system can combine these indicators into a graph structure similarity score, which serves as the basis for determining whether a candidate project enters the migration chain.

[0059] For example, consider a 110kV mountain transmission line project. The system retrieves Project A, Project B, and Project C from the historical project database. Project A has a structural similarity of 0.86 with the project under evaluation, but their market price conditions differ significantly. Project B has a structural similarity of 0.78 and similar transportation conditions. Project C has a structural similarity of 0.80 and similar policy cost boundaries. The system can write Project A into the strong constraint layer to provide basic cost items; write Project B into the price adaptation layer to correct for transportation and material price differences; and write Project C into the policy correction layer to correct for land acquisition or crossing compensation costs. This forms a tiered migration chain.

[0060] The key to the ladder-style migration chain is that each subsequent chain level does not overwrite the results of the previous chain level. Instead, it only accepts migrateable structural units and converged region-sensitive relationships from the previous chain level that have passed consistency verification. If a structural unit in the strongly constrained layer is determined to have an inconsistent cost caliber during consistency verification, this structural unit will not enter the price adaptation layer. Instead, other source region engineering subgraphs will be selected from the candidate set to supplement it. This chain-receiving mechanism prevents erroneous migrations from the previous layer from being amplified in the next layer.

[0061] Furthermore, the system can set hierarchical exit rules for the stepped migration chain. If a certain level fails two consecutive verifications, the system can increase the similarity threshold for that level, or delete the corresponding source engineering subgraph and rearrange the candidate set. If the difference correction amount in the price adaptation layer continuously exceeds the cost range boundary, the system can reduce the weight of the price adaptation layer and prioritize selecting engineering subgraphs near the target region. Through hierarchical exit rules, the system can maintain the stability of migration results when the sample quality is insufficient.

[0062] Furthermore, the system outputs a hierarchical record at each chain level. This record includes at least the source region engineering subgraph identifier, the reason for entering the level, a list of transferable structural units, a list of region-sensitive relationships, verification status, and convergence status. When a subsequent chain level reads the hierarchical record from the previous chain level, it only inherits objects with a verification status of "passed" and a convergence status of "converged." For objects that fail verification or are not converged, the system re-places them in the candidate set for replacement matching. Through this process, the step-by-step migration chain can form a verifiable hierarchical transfer process.

[0063] Based on the first embodiment of this application, in the fifth embodiment of this application, the same or similar content as the above embodiment can be referred to the above description, and will not be repeated hereafter. On this basis, the migration calibration cost item in the embodiments of the present invention can be generated in the following manner.

[0064] The system reads the transferable structural units in the strongly constrained layer and writes them into the basic cost item. The basic cost item can come from the historical cost object corresponding to the transferable structural unit in the source area engineering sub-drawing. If the project to be evaluated and the source area project are consistent in structural scope, functional scope, and pricing scope, the system uses the cost object as the basic cost item; if any scope is inconsistent, the cost object enters the calibration set and is not directly reused.

[0065] The system reads the target area price conditions in the price adaptation layer and writes the price difference correction amount into the price sensitivity relationship. The price difference correction amount can be determined by the difference between the target area price and the source area price, as well as the corresponding project quantity. For example, if the price of a certain type of material in the source area is 150 yuan / unit, and the price in the target area is 180 yuan / unit, with a corresponding project quantity of 1000 units, then the price difference correction amount is 30,000 yuan. The system writes this price difference correction amount into the cost range defined by the design condition grid without changing other cost objects.

[0066] The system reads the cost boundary of the target area in the policy correction layer and writes the boundary correction amount for policy-sensitive relationships. The cost boundary can be an upper limit, a lower limit, or a range. For example, if the allowable range for land acquisition compensation in a target area is 80,000 to 120,000 yuan per kilometer, and the historical cost in the source area is 60,000 yuan per kilometer, the system does not directly amplify it according to the price ratio. Instead, it writes the boundary correction amount in the policy correction layer to ensure that the result falls within the cost boundary of the target area.

[0067] When merging basic cost items, differential adjustment amounts, and boundary adjustment amounts, the system can merge them according to the cost object code. If two adjustment amounts apply to the same cost object, the system first determines whether they are mutually exclusive adjustment amounts; if they are mutually exclusive, the one with the higher sensitivity level is retained; if they are not mutually exclusive, they are superimposed according to the cost range boundary. Through the above merging method, the system can prevent the same cost object from being adjusted repeatedly.

[0068] Prior to the merger, the system standardized the basic cost items provided by engineering sub-maps from different source regions. Specifically, the system generated normalization coefficients based on cost object codes, unit of work, pricing stage, and fee calculation method, converting the costs from the source region into unit costs or quantity costs consistent with the project to be evaluated. For cost objects lacking unit of work, the system used the engineering scale factor of the corresponding map object for conversion. The normalized basic cost items were written according to transferable structural units and were no longer involved in the duplicate calculation of regional price differences.

[0069] The merging of values ​​for the same cost object is performed in the following order: structure, then price, then policy, and finally trimming. The system first writes the normalized basic cost item, then adds the price difference and the quantity adjustment, and then applies boundary adjustments according to the policy cost range of the target area. If the policy boundary is the upper limit, the portion exceeding the upper limit is trimmed to the upper limit value; if the policy boundary is the lower limit, the portion below the lower limit is supplemented to the lower limit value; if the policy boundary is a range, the adjustment result is limited to that range. Mutually exclusive adjustments are identified through cost object codes, condition layer identifiers, and adjustment type identifiers. When two adjustments both apply to the same cost object, and one adjustment is based on a change in the quantity of work while the other adjustment is based on the original quantity of work remaining unchanged, the system considers them mutually exclusive and retains the adjustment with the higher sensitivity level or higher source level priority.

[0070] The final cost assessment results are summarized according to the cost object code. The cost of each item is composed of the basic cost item after reduction, the price adjustment, the quantity adjustment, and the policy boundary adjustment. The overall cost is the sum of the costs of each item. The system synchronously outputs the source area engineering sub-map, sensitivity level, adjustment type, and cost boundary corresponding to each item cost, so that the cost assessment results can be reviewed and traced.

[0071] Based on the first embodiment of this application, in the sixth embodiment of this application, the same or similar content as the above embodiments can be referred to the above description, and will not be repeated hereafter. On this basis, the reverse back-feedback consistency verification in the embodiments of the present invention can be further processed as follows.

[0072] After obtaining the migration calibration cost item, the system performs a reverse restoration of the migration calibration cost item according to the source region conditions, and writes the reverse-restored verification cost item into the corresponding source region engineering sub-graph. It should be noted that the reverse writing involves switching the target region conditions to the source region conditions in the temporary calculation space, and performing reverse parameter replacement on the difference correction amount, engineering quantity correction amount, and boundary correction amount.

[0073] Specifically, for price-sensitive relationships, the system rewrites the difference between the target region price and the source region price as the difference between the current price and the historical price of the source region; for design constraint-sensitive relationships, the system restores the target region's engineering quantity correction according to the source region's constraint parameters of the isomorphic map object; for policy-sensitive relationships, the system replaces the target region's cost boundary with the source region's historical policy boundary. The verification cost item obtained after the above reverse parameter replacement is used to verify whether the same calibration model can be restored to near the historical cost of the source region under the conditions of the source region.

[0074] The system recalculates the itemized costs and overall costs in the source area's engineering sub-map based on verified cost items. Itemized costs can include building construction costs, installation costs, equipment purchase costs, and other expenses; they can also be subdivided according to power transmission and transformation specialties into civil engineering costs, equipment costs, line material costs, construction measures costs, and policy-related costs. The overall cost is the sum of all itemized costs.

[0075] The system compares the recalculated cost with the historical cost of the source region. A preset deviation range of ±5% can be set, or different ranges can be set for different cost items. For example, the deviation range for equipment purchase costs can be set smaller, while the deviation ranges for construction measures costs and policy-related costs can be set larger. If the recalculation deviation is within the preset range, it indicates that the same calibration model can maintain a reasonable cost structure under the conditions of the source region. If the recalculation deviation exceeds the preset range, it indicates that there are anomalies in the current calibration rules, the engineering sub-map of the source region, or the hierarchical transfer results, and the calibration results of the target region itself will no longer be used as a direct comparison object for the historical cost of the source region.

[0076] If the deviation exceeds the preset deviation range, the system first locates the cost object and sensitive relationship to which the deviation belongs, and then narrows the corresponding correction range or reconstructs the step-by-step migration chain. Narrowing the correction range can be achieved by reducing the difference correction amount, shrinking the cost boundary, downgrading the sensitivity level, or deleting mutually exclusive corrections; reconstructing the step-by-step migration chain can be achieved by increasing the similarity threshold, replacing the source region engineering subgraph, or adjusting the chain hierarchy order.

[0077] It should be noted that the reverse regression consistency verification is performed internally within the system to check the migration calibration logic. The verification object is the cost item after reverse reconstruction from the source region conditions, not the final cost assessment result of the target region. Traditional calibration methods typically only focus on whether the results in the target region are close to expectations. This application, however, simultaneously checks whether the same calibration model can still maintain a reasonable historical cost structure under the source region conditions, thereby reducing over-calibration, abnormal calibration, and sample migration errors.

[0078] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the cost management method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0079] This application also provides a design-cost linkage management system based on a knowledge graph for power transmission and transformation engineering design. Please refer to [link / reference]. Figure 3 The design cost linkage management system based on the knowledge graph of power transmission and transformation engineering design includes: The acquisition module 10 is used to acquire the engineering design elements and target area condition groups of the project to be evaluated in response to the request for cost assessment of power transmission and transformation projects. Module 20 is invoked to call the knowledge graph of power transmission and transformation engineering design and map the engineering design elements into standardized design subgraphs. Traversal module 30 is used to traverse the atlas objects in the standardized design sub-graph and mark the regional sensitive relationships. The regional sensitive relationships are written by the design condition grid to the influence position between the regional condition group and the atlas object. The atlas object includes design nodes, design relationships and cost items. Output module 40 is used to retrieve the engineering sub-map of the source region, construct a stepped migration chain, reuse the migrateable structural units along the stepped migration chain and calibrate the region sensitivity relationship, and output the cost assessment result.

[0080] The cost management system provided in this application employs the cost management method described in the above embodiments, which can solve the technical problems of difficult interpretation of regional deviations, insufficient sample size for zonal modeling, and unstable calibration results in the cost assessment of cross-regional power transmission and transformation projects. Compared with the prior art, the beneficial effects of the cost management system provided in this application are the same as those of the cost management method provided in the above embodiments, and other technical features in the cost management system are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0081] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0082] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct or indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A design cost linkage management method based on a knowledge graph for power transmission and transformation engineering design, characterized in that, The method includes the following steps: In response to a request for cost assessment of power transmission and transformation projects, obtain the engineering design elements and target area condition groups of the project to be assessed; The power transmission and transformation engineering design knowledge graph is invoked to map the engineering design elements into standardized design subgraphs; Traverse the atlas objects in the standardized design sub-graphs and mark the region sensitive relationships. The region sensitive relationships are written by the design condition grid to the influence position between the region condition group and the atlas objects. The atlas objects include design nodes, design relationships and cost items. Retrieve the engineering sub-map of the source region, construct a stepped migration chain, reuse the migrateable structural units along the stepped migration chain and calibrate the region sensitivity relationship, and output the cost assessment result.

2. The design cost linkage management method based on power transmission and transformation engineering design knowledge graph as described in claim 1, characterized in that, Before calling the power transmission and transformation engineering design knowledge graph to map the engineering design elements into standardized design subgraphs, the method further includes: Obtain a collection of engineering data for historical power transmission and transformation projects, wherein the collection of engineering data includes at least design data, inventory data, pricing data, and regional data; Analyze the engineering design elements in the engineering data set and uniformly encode synonymous elements, heteronymous elements, and default elements; The coded engineering design elements are grouped into design entities, constraints, and cost objects. Based on the relationships between the design entities, constraints, and cost objects, a knowledge graph for power transmission and transformation engineering design is formed.

3. The design cost linkage management method based on the knowledge graph of power transmission and transformation engineering design as described in claim 1, characterized in that, The power transmission and transformation engineering design knowledge graph is invoked to map the aforementioned engineering design elements into standardized design sub-graphs, specifically including: Analyze the component parameter information and constraint parameter information in the engineering design elements; The component parameter information is converted into standard component nodes in the power transmission and transformation engineering design knowledge graph, and the constraint parameter information is converted into standard constraint relationships in the power transmission and transformation engineering design knowledge graph. The standardized design sub-drawing is obtained by completing the connection relationships between the standard component nodes, the standard constraint relationships, and the corresponding cost items.

4. The design cost linkage management method based on power transmission and transformation engineering design knowledge graph as described in claim 1, characterized in that, The design condition grid uses regional condition groups as the row dimension and map objects as the column dimension. Each cell contains the sensitivity level, migration attribute, and cost range. The sensitivity level is rewritten into the standardized design sub-graph as the target regional condition group changes.

5. The design cost linkage management method based on the knowledge graph of power transmission and transformation engineering design as described in claim 1, characterized in that, Retrieve the engineering sub-map of the source region and construct a tiered migration chain, specifically including: Obtain the set of historical project sub-graphs and delete historical project sub-graphs whose hard engineering conditions are inconsistent with the project to be evaluated; Calculate the graph structure similarity between the remaining historical project sub-graphs and the standardized design sub-graphs, and arrange the historical project sub-graphs that meet the similarity threshold hierarchically according to the constraint strength of the regional condition group; The arranged historical engineering subgraphs are sequentially written into the chain migration sequence to obtain the ladder migration chain.

6. The design cost linkage management method based on the knowledge graph of power transmission and transformation engineering design as described in claim 5, characterized in that, The stepped migration chain has a chain-like hierarchy consisting of a strong constraint layer, a price adaptation layer, and a policy correction layer. Each subsequent chain-like hierarchy only receives the verifiable migrateable structural units and converged region-sensitive relationships from the previous chain-like hierarchy.

7. The design cost linkage management method based on the knowledge graph of power transmission and transformation engineering design as described in claim 6, characterized in that, The method further includes reusing the transferable structural units along the stepped migration chain and calibrating the region-sensitive relationships, and also includes: In the strongly constrained layer, the transferable structural units that meet the hard engineering conditions are locked and the corresponding basic cost items are written. In the price adaptation layer, read the price conditions of the target area and write the difference correction amount for the price sensitivity relationship; in the policy correction layer, read the cost boundary of the target area and write the boundary correction amount for the policy sensitivity relationship. The basic cost item, the difference correction amount, and the boundary correction amount are combined to obtain the migration calibration cost item.

8. The design cost linkage management method based on the knowledge graph of power transmission and transformation engineering design as described in claim 7, characterized in that, The transferable structural unit is configured to satisfy the consistency of structural caliber, functional caliber, and pricing caliber in both the source region engineering sub-graph and the standardized design sub-graph, and the transferable structural unit does not receive region-sensitive relationships marked as highly sensitive by the design condition grid.

9. The design cost linkage management method based on the knowledge graph of power transmission and transformation engineering design as described in claim 7, characterized in that, After obtaining the migration calibration cost item, the method further includes: The migration calibration cost item is reverse-engineered according to the source region conditions and then written into the corresponding source region engineering sub-graph. The cost of each item and the overall cost in the engineering sub-drawings of the source area are recalculated to obtain the recalculated cost, and the deviation between the recalculated cost and the historical cost of the source area is compared. If the deviation exceeds the preset deviation range, the correction range of the migration calibration cost item is narrowed or the step migration chain is reconstructed in a preset manner.

10. A design-cost linkage management system based on a knowledge graph for power transmission and transformation engineering design, characterized in that, The system includes: The acquisition module is used to obtain the engineering design elements and target area condition groups of the project to be evaluated in response to the request for cost assessment of power transmission and transformation projects. The calling module is used to call the knowledge graph of power transmission and transformation engineering design and map the engineering design elements into standardized design subgraphs. The traversal module is used to traverse the atlas objects in the standardized design sub-graph and mark the region sensitive relationships. The region sensitive relationships are written by the design condition grid to the influence position between the region condition group and the atlas object. The atlas object includes design nodes, design relationships and cost items. The output module is used to retrieve the engineering sub-map of the source area, construct a stepped migration chain, reuse the migrateable structural units along the stepped migration chain and calibrate the area sensitivity relationship, and output the cost assessment result.

Images